Adam,

In the future, it would help greatly if you post the error that you are getting. This was an easy one, but if you know the error, why...

Your best bet would be to make sure ALL inserts and updates are done through stored procedures and then code the value check into the stored procedure. For example,...

Depending on your definition of 'downtime' this is not possible. At some point, users will need to be disconnected from the old database and connected to the new database....

I'm not sure if you can post it on a web-site, but I do know that you can call it in. You could go to the MS web-site and...

I too tried the spell check for the first time today. It appears to catch the spelling mistakes, but I have no idea where to go from there as...

This is surely odd. This may be a good time to get big brother Microsoft involved.

They will all produce an error if you change the date format. We must assume here that the varchar date value that they are placing on the right side...

I've created your tables/defaults/sp's here on my testDB with some sample data and I cannot reproduce what you are seeing. You say you get this whether you run your...

Lionel2007,

It looks like your scope is creeping a bit here. Can you post the table DDL for the tables you'd like to copy over. If there are...

All 3 version of this query are read by the Query Optimizer in the same way: the string date on the right side is implicitly converted to datetime. Because...

An undersized TempDB can cause performance problems as SQL Server must grow the TempDB to handle the throughput. In your case, your TempDB has grown quite and bit. ...

Maybe it's me who's blind, or maybe just confused becasue the OP hasn't defined what he wants real well. I was under the impression from the first post in...

That's still an INNER JOIN Felix.

Marcus,

Either try Scott C.'s or Remi's suggestion or post your sample data and expected result so the rest of us have something...

Assuming there are no identity columns and that both DBs are on the same server, this should work:

INSERT INTO destinationDB..TableName

SELECT *

FROM sourceDB..TableName

Yes. If you want to lengthen a column, use ALTER TABLE to assign new data length. If you want to shorten the column, you'll want to...