argg... that's supposed to be <dbname>

I love it.... and coincidentally I was working in the same problem but from a Powershell angle. Now I don't have to.

BTW... why do you have this:

your your WHERE statement:

andjob.name...

I like the article.

and yes yes... you can do it easier with SQL statements like Jeff says... but what I like about the article is that is uses a very...

rachilles (5/13/2015)

---

Great article, and very timely for me.

In the Virtual Disk presentation illustrations, it shows a disk cylinder with OS, Data and Logs all in one cylinder, seemingly attached to...

Thank you so much Learn2Live. Your high level steps are great

And Perry Whittle... oh oh oh.... that's paper.. great find.

That's exactly what I needed

My biggest question as... can we somehow...

Yes, you need to remove TDE from the database, and don't forget to truncate the Tlog.

I had to do something similar. it was a nightmare!

1- make sure it's on FULL...

Wow.. and i thought i was bitter.

honestly, I'm in the US, in the Midwest. The nice kitchen factor maybe an issue in the coast, but over there is no...

I work in a huge corporation. My building is in a small town and it employs nearly a thousand people.

Kitchen is a joke. I never eat there... i...

while it's a bad idea to switch recovery modes... the OP wants a safeguard in case that happen... besides you can't run a Tlog either on a newly created database,...

Gary Varga (9/30/2014)

I would like to commend you on not wanting to plagiarise nor wanting to repeat existing posts. However, don't forget that a tutorial is different to a post...

very inspirational post, thanks.

I've been thinking about blogging for a while, and the most compelling reason is career development and a way to showcase my work.

however, the most powerful excuse...

Hello,

Will, BillHol gave me lots to think about.

In this particular case, since it's only a handful of people trying to run the job "once in a while", I guess we...

holy camoly!

I found the problem!

The key was that I stopped it. I stopped/cancel the sp_removeDBReplication

which if we couple with the other error:

"Transaction count after EXECUTE indicates a mismatching number...

Yes, however, step three is

And that's the problem... It runs and run and I'm not...

It's nice that SQL2008R2 now has that DVM.

But for other systems, we can use a more... let's call it brute

----------------------

declare

@VirOrPhys[nvarchar](50),@manu-2[nvarchar](50)

create table #OSinfo(OSinfo varchar (255))

insert into #OSinfo

exec master..xp_cmdshell 'systeminfo'

set...