A long time ago--ok, file timestamp says 5 months, but I don't remember doing any of it--I created a simple VB script utility to script out all the jobs from...

If the upgrade calls for RS to be up and running during the upgrade, then any patches that needed to be made to the DBs themselves will be made to...

This is a very deep topic, and one that we almost went with but didn't ($$$). So I've thought about it, but have no practical experience. And so, having presented...

Here's some templates I've used in the past. They're somewhere between SQL 2000 and SQL 2005 compatible, as I haven't done much work with this yet in 2005, so be...

Off the top of my head, I'd suggest something like this:

1) Build a two-node cluster, install one, maybe two instances of SQL on it (depends on what you've got in...

Oh, the usual--code gone wild. There have been a number of similar situations, and they generally fall back to the fact that SQL Server isn't all that good at running...

So here's your real problem, and your real question: How did the Production database get to be so significantly different (I consider all triggers to be significant -- and you...

At my current position, one of the first things I do when things start acting up is to check available hard drive space. We have a lot of processes that...

Any chance that there's an (enbled?) trigger on Production that's not on Dev? Or perhaps some refresh routine that comes in after your update?

Some investigating queries I'd try:

-- Test...

(Sorry if this has already been griped about, but I'm in a bit of a rush.)

After a mere two minutes, I can freely state that I loathe your revised search...

Cool! New toys to play with tomorrow!

But years of pain force me to ask: is there an "unmark" procedure?

Philip

Bob's pretty much got the issue right. As another example (and a useful utility when working with unfamiliar databases) here's what I've been working at.

Here's the original version. When run...

I've been doing the "shorthand", not specifying the (current) database name. (One reason I used the "sp_" naming convention...)

   Philip

I while ago, I picked up the following practice:

 - Create a SQL authenticated "DBA" login, give it SysAdmin rights, use it whenever I need to use such a thing.

 - Generate...

The original point of the article was essentially about using the SQL Server 2005 client tools to manage SQL Server 2000 instances. Based on my experiences of the past few...