Really, without getting into backups, the easiest way I can see to do this is the capture the data in a table. If you need to know the value...

One way to do this is to encrypt sensitive fields in the application (and store the encrypted value in the database). Not all of the data, just the columns...

I agree with the consensus that one big DB is much easier at this stage. I would suggest you include a customer_id (or whatever the PK is at the...

I think we need to consider what this actually proves, though -- if people get Vista with a new machine fast enough to handle it, with plenty of RAM, and...

I think you may be misinterpreting compatibility. I think it's BACKWARD compatibility. Meaning, they let you create duplicate indexes in previous versions. If they disallow them now,...

Yes, I read what you wrote earlier. I'm just saying I don't believe it's how you populated your grid that's the problem, it's the insert/update. I don't think...

This proc almost certainly isn't the problem. Your problem is with the insert/update.

Your PK violation isn't coming from a select statement (unless it's something tangential, like you aren't selecting...

I'm not completely clear what you're trying to do. You mention leaving the primary key null, but you can't insert nulls into a primary key either . . .

This...