We had a similar-sounding situation a few years ago, where we couldn't use the DR system and didn't know the data at any given time but still had to prove...

If you leave it at the default then it can choose a different TCP port after a failover or other restart. Hard-coding the TCP port that each SQL Server...

By default each SQL Server instance will choose a random free TCP port at startup. When a client tries to connect to a server/instance without specifying the TCP port

...

I'm assuming Col1 is a character field. If not you'll need to cast/convert it to a char.

If the value is always the same as the first character, use:

...

A reboot of the server will resolve the problem in the short term, but you'll get the same problem again sooner rather than later.

We've found we've had to add the...

The least-downtime way to do it for one database that we've found is to:

1. Put the database into full recovery if it's not already

...

We've found that SQL2k5 seems to be more sensitive to variations in statistics, in that bad query plans (ie. slow) are more likely to be used than when the statistics...

It is possible to have SQL2k and SQL2k5 running under two virtual servers in a cluster. It's something we have used temporarily during in-place upgrades, although we've never run...

From the error I suspect it's something to do with what you're trying to write to the last 3 fields.

My guess is the last field, [blogsummary]. What are you...

This is one of the things I loathe about SOx and all the other audits I've had to deal with. I've never been given a document saying "this is...

I think your best choice here is to rename the existing table, create a new table with the old name, migrate all the existing records into the newly-created table with...

As a very broad generalisation I would expect a reporting system to access more data and so to benefit more from additional memory than a (well-written) transactional system, where the...

There's a couple of things I can suggest:

1. Why is the join to the product table there? That's not used anywhere in the statement but will...

Yet another arguement for keeping the database and application on separate servers.

I know it's not a definitive proof, but we've migrated a significant number of application databases (~100) from SQL2k/32...

As always, it depends, but we've always found it better to update the stats comparatively frequently (weekly is our standard), particularly under SQL2k5 where we've found queries against tables with...