There isn't necessarily anything wrong with a multi-column key, I agree. Strong RI declared will keep things in sync, but I find having all those columns in all tables cumbersome....

You could replicate to a central server, but you'd have to address ID issues. Most centralization schemes have to solve this problem and there isn't a good way to do...

I think I like the last advice. Mimic the production environment and keep the names the same. A linked server also works, but be sure you use different accounts in...

I've used domain accounts or "sa", but don't use any other user accounts. Can cause issues at times.

How did you move the database? Are you getting similar resource counters on the new Amazon db? Are you sure there isn't network traffic delaying things?

I might update statistics as...

The files don't change from 32 bit to 64 bit. Only operations in memory are different (using 64 bits instead of 32).

There are some driver issues in a few places,...

That procedure stops a job that is running. It doesn't disable a job.

You need sp_update_job (http://msdn.microsoft.com/en-us/library/aa260379%28SQL.80%29.aspx)

They can run together, but I usually offset them to avoid resource contention issues.

You cannot count on the larger file being more recent. Use the RESTORE HEADERONLY commands to determine the content.

Hasn't come back to haunt me. I almost never use that stuff. I backup to disk files, name them by date, use that for restores.

deletes

Most DR solutions include log shipping...

• This reply was modified 7 years, 3 months ago by Steve Jones - SSC Editor.
• This reply was modified 5 years, 11 months ago by Dave Convery.

Yes, the ramification is that you can't query for what is contained in a backup or have SSMS automatically do a restore. The history cleanup task in the maintenance plans...

I have had some people say they burned up SSDs, but I think that was under extreme load. I have had a few people say they have used SSDs in...

I think something like a SQL Refactor from Red Gate would do this.

Are you not using Source Control? I would make sure you're doing that, and then I would look...

I would follow Lowell's advice. You need a unique constraint to ensure your data is intact, but there's no need to copy all that data over to a FK table.

You don't necessarily need to tune the design. I would move to varchar as it can save some space, which might end up making your rows denser on the tables.

If...