We're in the testing phase of our upgrade, and we've noticed that in just one table (so far anyway), there are several rows missing. Not on any huge scale, we're missing 78 out of almost 400,000 rows, but we really need to have everything. We're running both servers parallel for testing purposes, and the old server is linked from the new one. We're using named pipes in the upgrade wizard. Once we figure out where all the issues are and how to fix them, we're going to wipe and re-install the new server, and re-run the upgrade. The old box is still our production server right up until the point we go live.
More to the point, I'm trying to create a query that will return the rows from the old server that don't exist in the new one. I've tried a couple things using the NOT EXISTS operator but so far have had no luck. I figure if nothing else maybe once I'm able to select these rows I can select into the new database.
Upon inspecting the logs for the upgrade I found that the table in question had a lock on it. SQL Executive was stopped, and I'm 95% certain that nobody was accessing the DB through their client applications at the time. Any ideas for other sources of interference I should check for and block out while running the upgrade?
Thanks! Marc Creviere
More to the point, I'm trying to create a query that will return the rows from the old server that don't exist in the new one. I've tried a couple things using the NOT EXISTS operator but so far have had no luck. I figure if nothing else maybe once I'm able to select these rows I can select into the new database.
Upon inspecting the logs for the upgrade I found that the table in question had a lock on it. SQL Executive was stopped, and I'm 95% certain that nobody was accessing the DB through their client applications at the time. Any ideas for other sources of interference I should check for and block out while running the upgrade?
Thanks! Marc Creviere