I'd agree as well. I search for fit first, technical experience/challenge next. Not that technical skills aren't important, but I think that the people are more important.

In terms of DR, perhaps something that examines the cost of data loss and the risk factors and maybe determines some formula for how much $$ should be spent?

For procs,...

Polyserve is the only software I'm aware of that's like this.

The simple view is:

- Full backups copy all your data, permissions, schema, from the database to a file that you can use to restore them. They don't handle logins, so...

Good to see you're still around, Barry. Hope things are going well for you.

Welcome back.

I don't think you want me singing

Aleve

my back is tight today

SQL Server is huge, and the explanation would be pages and pages.

Please go read some documentation. There are good explanations here: http://msdn.microsoft.com/en-us/library/cc280361%28v=SQL.100%29.aspx

If there's something specific you don't understand, ask. Otherwise,...

Good advice above. I would tend to only consider splitting things if I expected scalability to require me to have 3 servers in the future to support the load.

Otherwise,...

I think you can timewarp ahead on Sun night if you like. Or you could probably find a podcast or two now 😉

homebrew01 has a good point. Check free space in logs/data files, and see if you can make some.

However if you are truly out of space and need to extend things,...

I still prefer the ID. I see the point that countries are standard, but in my lifetime, names have changed quite a bit. That's not a huge problem for updates,...

Yes, potentially. Do you have a filegroup backup?

http://msdn.microsoft.com/en-us/library/aa337540.aspx

Check the default trace: http://www.sqlservercentral.com/articles/SQL+Server+2005/64547/

Alvin Ramard (8/27/2010)

---

This one really boggles the mind.

Mistake #1: No regular backups

Mistake #2: Cut & Paste DB files (Always COPY, never CUT)

Mistake #3: Deleted records from all the tables

Mistake...