I'm not sure I'm The Man, but thanks.

I wouldn't necessarily discount replication. As Bru mentioned you can have issues with pushing this data to the same destination. There are a...

Rambilla,

The current released version of SQL Server is SQL Server 2008. It has one service pack, having been released in Aug 2008 and it is fine for production. You need...

River1,

There usually is some planning for the next version as the current one is being finished. In other words, AFAIK, right now there are

- Support people working on patching SQL...

Or do a simple search of scripts built by the developer. If they can't remember to add dbo., perhaps you can reject their scripts until they do

Encrypt only the credit card column, or better yet, encrypt it as a hash only. Don't store this stuff if you don't need to do it. If you do, then...

Please don't use "sa" in examples. It sends a bad message, even though it doesn't matter in this example.

However, the way you want to do this, using the code above,...

I think that the default response ought to be to help out. That's what we do as technologists, and our art/science is often arcane and complex in the eyes of...

Here's a good hint for you:

http://www.sqlservercentral.com/scripts/Triggers/63064/

I had a friend that had a multi-client scenario where each client had their own database. They had a central database with some common information which was replicated to each...

Correct, you must user server software for server versions. If you are trying to save money on licensing the server, you won't. You'll get yourself into trouble if you figure...

If you have some idea of the path that will come in, you can search through it with Charindex to find the last "\" and then use substring to get...

If you have the data, that's the way I'd go.

I was going to suggest using backup sizes, which is how I've tracked database growth over time. I have autogrow set...

This looks like homework. You ought to be able to easily search out the first and third items. A few links for you to read:

http://blogs.msdn.com/craigfr/archive/2006/08/10/687630.aspx

http://blogs.msdn.com/craigfr/archive/2006/08/03/merge-join.aspx

http://blogs.msdn.com/craigfr/archive/2006/07/26/679319.aspx

I'm with Jeff. I like them in separate fields, and then assemble them in another field if needed. As numerics they sort well, and the separation to me makes it...

How much data are we talking about? Is there a reason you don't want to move the whole db?

Most people I know transfer data in bulk at specific intervals so...