The easiest ways I know are:

1) Detach the database, move the files, reattach.

2) Backup the original, drop the database, restore with the new path.

Guarddata-

Another thing to consider is the indexing and number of rows involved. We have many situations where running a UNION or a CURSOR, with each query specific to a...

Let me emphasize the point that the Log backup should be done without truncating. It sounds as though you are running the log backup - and the replication nightly....

Rather than truncating and shrinking the log file, could you just perform a log backup? This would allow total usage to remain fairly constant, improves performance slightly since you...

eletuw...when you way the output is sent to a text file, what method are you using to send it? Is this a DTS routine? a query in bcp?

Guarddata-

...

Sorry - I guess I don't know what you mean by that term. I have heard of clustered machines or the Enterprise system of using multiple machines as though...

What are you using to get the result datasets? When you run this in QA, can you run each select and obtain results?

If you are reading the data with...

For a more detailed description, I recommend the Books on Line (BOL)...

The quick answer is that clustered indexes allow ordering of the data as the leaf node of the clustered...

Updating a million rows at a time is still an awful lot. It looks like you have the luxury of not needing access to the database during this update...

Oops - you are correct Vladan, I got the parenthesis mixed up

Still - I think there are three conditions. As you say - it does...

OR in a where clause is too often a signal for a table scan. Where possible, and this looks like a good time, break the commands into separate, precise...

This may be a naive question.... Why not just remove the NOLOCK hint from BTable so it gets held in a transaction. Seems like you wouldn't need to worry...

Any triggers that are being fired off?

Guarddata-

My guess is that the database properly holds the NULL value. The last time I saw this problem, I had to play with the settings in the ADO recordset...

Looks like confusion in the syscolumns table. I would take mom's advice and just rename, create new, copy the data.

Guarddata-