Noted, my apologies, didnt read the question thoroughly.

🙂

Please explain why you would recommend a nested select on the same table, looking for NOT IN on the same column, instead of selecting it and excluding the undesired data?

I would recommend Full on production, but read up on the different types and decide which suites your environment and needs best:

http://msdn.microsoft.com/en-us/library/aa173531(SQL.80).aspx

SSPI:

http://msdn.microsoft.com/en-us/library/aa380493(VS.85).aspx

Use SSPI in your web.config, and use an application role, where the ID & Pwd will be save and encrypted in SQL Server.

Suggest you set your credentials in the data source and not the actual report.

these sp's, what is your naming convention? please tell it's not SP_yourspcustomnamehere?

I agree Steve, and for some weird reason, when opening a post with garbled code and lines of results, erm.. it makes one want to look the other way.

Not because...

constraint is stopping the insert as a result of trying to create duplicate keys.

specify your process to copy...

MS Press Books

BOL

and a lot of SSC reading.

It's true, going virtual holds a lot op pro's but also cons.

Weigh up the options, and the money you are going to spend, versus your needs.

It can go both ways,...

I agree, take the current backup and rather restore it as the new name.

This will keep structure etc i place.

You cant host 2 DB's with the same name in the same SQL instance, even if you have different filenames.

Each DB name has to be unique.

Read up on Gail Shaw's blog, lots of info and help on all types of Indexes.

http://www.sqlinthewild.co.za

She's a ninja when it comes to Indexes.