John W. Colby
jcolby at colbyconsulting.com
Tue Feb 25 14:33:29 CST 2003
OK, I just looked. If there were, there aren't any more. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-admin at databaseadvisors.com [mailto:dba-sqlserver-admin at databaseadvisors.com]On Behalf Of Billy Pang Sent: Tuesday, February 25, 2003 3:07 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer]Cross Posted - Upsizing fails On the machine that is trying to access the newly installed ss2k, check the Client Network Utility. There might be an old alias in there. Billy >From: "John W. Colby" <jcolby at colbyconsulting.com> >Reply-To: dba-sqlserver at databaseadvisors.com >To: <dba-sqlserver at databaseadvisors.com> >Subject: RE: [dba-SQLServer]Cross Posted - Upsizing fails >Date: Tue, 25 Feb 2003 00:52:25 -0500 > >Ooooh isn't that embarrassing! Sorry. > >Yes, this SQL Server is on another box. The SQL Server physically resides >on my old dual PII 233 machine, which is the one I reformatted and >re-installed on. > >I work on my dev machine which is my "new" AMD Athlon 1.33ghz, running >Win2K >Pro. It has the EM installed on it as well, and had been talking to the >SQL >Server on my "old server" (which was wiped out). Thus I am sure there is >something somewhere that tells everything that said server existed. I get >the feeling that the tables that failed to import did so due to an "order" >problem. At the time it tired, something else it needed (a parent table) >wasn't moved yet. That kind of thing. With only 4 missing it will be easy >enough to drag them in I think. > >John W. Colby >Colby Consulting >www.ColbyConsulting.com > >-----Original Message----- >From: dba-sqlserver-admin at databaseadvisors.com >[mailto:dba-sqlserver-admin at databaseadvisors.com]On Behalf Of Francisco >Tapia >Sent: Tuesday, February 25, 2003 12:42 AM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer]Cross Posted - Upsizing fails > > >you forgot the "co", Francis + co = Francisco :D > >Glad it worked out for you... I don't really see how you could have even >seen the old server from .net if you wiped out the system, I mean that >would >have ment the whole registry would have gone with it too.. unless this is >on >another box? > >-Francisco >http://rcm.netfirms.com/ >----- Original Message ----- >From: "John W. Colby" <jcolby at colbyconsulting.com> >To: <dba-sqlserver at databaseadvisors.com> >Sent: Monday, February 24, 2003 9:23 PM >Subject: RE: [dba-SQLServer]Cross Posted - Upsizing fails > > >: OK, things are getting better. I found an article on the web that >mentioned >: that I had to create the database out in SQL Server first, which I did. >I >: then created a DSN (I think it is called) that pointed to this table, and >: ran my export. This time only a handful of tables failed to export. At >: least I have a place to begin looking at why, rather than a complete and >: total failure. It would be nice to know why the "create new db" won't >work >: though. >: >: John W. Colby >: Colby Consulting >: www.ColbyConsulting.com >: >: -----Original Message----- >: From: dba-sqlserver-admin at databaseadvisors.com >: [mailto:dba-sqlserver-admin at databaseadvisors.com] >: Sent: Monday, February 24, 2003 11:53 PM >: To: dba-sqlserver at databaseadvisors.com >: Subject: RE: [dba-SQLServer]Cross Posted - Upsizing fails >: >: Francis, >: >: As for "Where" it is coming from, I have no idea, but my guess would be >the >: registry. The new .net stuff just "found" the old sql server and gave it >to >: me as a choice in my combo of sql servers that I could attach to. I had >to >: go specify the new in order to get at the new. I also deleted the old >(from >: a right click menu in the wizard I was in in .net). >: >: As for what I did - I had Win2K Pro and SQL Server. I wanted to install >: Win2K Server which will not install "over" Pro. Due to the fact that I >also >: had dual boot to Unix that was on a disk that I removed, and such >ugliness, >: I decided to just format and start from scratch. So yes, I formatted the >HD >: and installed Win2K Server and SQL Server from scratch. >: >: SQL Server management console shows version 5.0 (build 2195: Service Pack >3) >: in the help about. >: Windows shows 5.00.2195 Service Pack 3 >: >: Because I put my data out in one of my data disks (partitions) for the >: previous install, the old SQL database (the databases themselves) >continued >: to exist after I reinstalled, however I had no idea how to get SQL Server >to >: talk to them, and I had nothing important in them anyway, so I think I >just >: blew them away. >: >: I just tried the upsize wizard again. The new SQL Server was the default >: server in the combo for selecting that. I selected new database and >called >: in something unique (not already in SQL Server). The wizard took off and >: ran in about 2 seconds (or less) came back with a "table was skipped or >: export failed" for every table. Going to EM there is no sign of a new db >by >: the name I specified. >: >: It looks like it just didn't do anything beyond generating a report that >it >: didn't do anything. >: >: John W. Colby >: Colby Consulting >: www.ColbyConsulting.com >: >: -----Original Message----- >: From: dba-sqlserver-admin at databaseadvisors.com >: [mailto:dba-sqlserver-admin at databaseadvisors.com]On Behalf Of Francisco >: Tapia >: Sent: Monday, February 24, 2003 11:14 PM >: To: dba-sqlserver at databaseadvisors.com >: Subject: Re: [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/ >: >: >: >: ---------------------------------------------------- >: Is email taking over your day? Manage your time with eMailBoss. >: Try it free! http://www.eMailBoss.com >: >: ---------------------------------------------------- >: Is email taking over your day? Manage your time with eMailBoss. >: Try it free! http://www.eMailBoss.com >: > > >_______________________________________________ >dba-SQLServer mailing list >dba-SQLServer at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >http://www.databaseadvisors.com > > > > >---------------------------------------------------- >Is email taking over your day? Manage your time with eMailBoss. >Try it free! http://www.eMailBoss.com ><< winmail.dat >> _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com ---------------------------------------------------- Is email taking over your day? Manage your time with eMailBoss. Try it free! http://www.eMailBoss.com -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 5024 bytes Desc: not available URL: <http://databaseadvisors.com/pipermail/dba-sqlserver/attachments/20030225/0c42b480/attachment.bin>