I am planning a migration from a 6.5 SQL Server to a second server running 7.0.
I tested the process by running the upgrade from our test server to the new
server and had no problems. This last weekend, I tried to test the migration
of our production server to the new SQL 7 server. Before running the upgrade I
rebuilt the master database on the 7.0 server to remove any remnants of the
test server databases. When I ran the migration, I received the following
error “The export server must be running Microsoft SQL Server 6.0 or 6.5”. I
tried pointing to the test server again and had no problem. I had the thought
that something was recorded about that particular server, so I pointed the
Migration process against another ofour test servers and it looked fine as
well. All three 6.5 servers I tried are running NT4 SP 6a and SQL 6.5 SP5a.
Our 7.0 server is running SP1.
Yesterday I tried the migration process using the DNS Alias instead
of our current server name,it gave me a
message indicating I needed to be an administrator on the 6.5 Server. That is
the error I expected to see since the login account was NOT an administrator on
the production server (I didn’t want the upgrade to start in the middle ofthe
day). Last night, I
added the AWSQLP03 id to the the administrators group on the LIFESQL3 server and tried the migration. It still generated the error about not being in the
administrators group. I then added AWSQLP03 to the administratorsgroup on the
test server and re-ran the migration of that server so we can continue with our
testing.
I also observed another interesting thing yesterday that looks somewhat security
related: I tried to do an NT authenticated connection to both test and
production from the 7.0 server. Both failed with the same message regarding not
being a valid login on the 6.5 server. The interesting thing is that one said
the u