Scott,

You've got quite a problem here and I'd really suggest engaging a consultant that can help you with more detailed designs for your environment.

You are tackling a few issues here...

I never noticed that. I'll take Chewbacca if no one else has him.

Very nice, Phil, and thanks.

It's right on that many of you out there have helped.

(post sneaked in from Keystone, CO )

I'm not sure how configurable this is. I'd have to dig into it and see if there's something we can do.

Most people don't enter a description, BTW. It's one...

Wow, brings back memories to go look at the v1 site. Very cool and thanks for the link!

It's hard to tell you what to do here. There are pros and cons to one or multiple tables.

I'd tend to split differing things into different tables, according to normaliztion...

SQL Server will respond to the shutdown message from Windows. I wouldn't pull the power plug, but I've restarted thousands of instances with Windows | restart with no issues.

What do you mean "create a database locally" With VS?

I'd use SSMS and be sure I created the database, then access it in the project.

Supported is important to know, and good points that the question should mention it. I've changed the question to show that.

Apologies on the XLS. It's attached now.

Gran Torino is on my list, but I'm not sure I'll see that before it gets out of theaters.

I did see Dark Knight, good in spots, but a bit long...

First Windows is bloatware, though now we have Server Core, which is stripped down and SQL is supposed to work on that. As far as *Nix, there are some fundamental...

Thanks again and hopefully we're not all wrong, Bob.

I really appreciate all the notes and this thread gets a smile on my face. Thanks for that.

tgarland sent me a note. I was slow to act, but I'm closing this thread. Anyone reading this, please use the link to hit the open one.

you can run this from SQLCMD (command line) and that would do it.