I've seen this same setup, and it makes sense to me. However I wouldn't centrally locate procs. I have had to move databases to new instances, for performance or security...

I have spoken with my boss, and in principle he thinks it's a good idea to help out here. Any preferences on what you're like in terms of a support...

I tend to agree with bitbucket. Hire a lawyer, decide what to do.

I might also spread the word to other consulting companies in the area that you have had issues....

pain

Nice article, I guess I will try to support those Royals since they're trying

that's great

🙂

Two things here.

1. You need code control.

2. You need a process for building the release.

#2 has lots of options.

For #1, I don't think it needs to be a dedicated QA...

Yep, second vote for you being correct. Let the backup complete *before* you start the release.

Is f: a local drive?

Check out sys.index_columns (http://msdn.microsoft.com/en-us/library/ms175105.aspx) and you can get the columns. If not, join with sys.columns and you should get the types.

You can't merge databases. You can merge the data in the tables, but there could be different logic for every table.

In terms of what you are doing with these...

No difference in how it will work. The 2008 instance will change the file format since that's the engine code, but the interpreter will handle code just like the 2005...

One other issue to consider is how do we decide what's on the test for new features? Who "becomes" the expert? The "who" can be a group, but how does...

I think PASS will need to back it at some point, but PASS is a volunteer organization, so it would be the same people here that would need it run...