[dba-SQLServer]Cross Posted - Upsizing fails

: Is there any way to get rid of all traces of, all references to, a sequel
: server that no longer exists?  Then set up Access to know about the SQL
: Server that does exist.  Then run the upsize.

You say there are traces of the old server name, where? through the UDL
interface? or through the wizard?  Did you re-format your entire system in
order to install Win2K server? what SP do you have installed on Win2K you
should have up to SP2 at the very least... And for SQL Server 2000 you
should have it up to SP2 to start, SP3, can cause some wierd abnormalities..
Once you have your Sp's up to SP2 for both the OS and SQL let us know how
that is looking... I'd like to keep this thread on the list in order to keep
it in the archives if you don't mind... :D
-Francisco
http://rcm.netfirms.com/
----- Original Message -----
From: "John W. Colby" <jcolby at colbyconsulting.com>
To: "AccessD-SQLServer" <dba-sqlserver at databaseadvisors.com>
Cc: "AccessD" <AccessD at databaseadvisors.com>
Sent: Monday, February 24, 2003 7:54 PM
Subject: [dba-SQLServer]Cross Posted - Upsizing fails


: Folks, I am trying to run the upsizing wizard on my client billing
database,
: and it is failing miserably.  Basically it thinks it is happening, and it
: thinks that some parts succeed (some tables) but nothing gets into the SQl
: Server database.
:
: I think that what might be happening is that I had a SQL Server system set
: up on my server.  I ended up completely re-installing windows in order to
: get Win2K Server edition installed (won't install over Win2K Pro).  Thus
my
: old SQL Server is now gone.  However I keep seeing references to that
server
: name (the machine itself was named something different, so I can tell).  I
: am guessing that it is trying to talk to that old SQL Server and it no
: longer exists.
:
: Is there any way to get rid of all traces of, all references to, a sequel
: server that no longer exists?  Then set up Access to know about the SQL
: Server that does exist.  Then run the upsize.
:
: BTW, back when I had the other SQL Server running, I had done this
: procedure.  I discovered things like bad dates that SQL Server couldn't
: handle (I used to use 1/1/1000 as an initialized date flag, which SQl
Server
: couldn't handle).  I also discovered the problem of random autonumbers
used
: for data synchronization in my old db wreaking havoc in SQL Server.  I
found
: and fixed all of these things and upsized this db in the past so I know it
: should work, and it should do so easily.
:
: I would like to use my billing application as a test bed for learning .net
: so I really need to get the upsizing happening.
:
: As an aside, I tried going at it from inside of SQL Server and managed to
: pull in about 1/2 of the tables.  No rhyme nor reason that I can see why
: some tables came right in and others didn't.
:
: Anyway, if anyone can talk me through troubleshooting this thing and
getting
: Access 2K upsizing working I would appreciate it.
:
: Thanks,
:
: John W. Colby
: Colby Consulting
: www.ColbyConsulting.com
: