Did Uninstall/Reinstall of SQL Server. Now databases are under WRONG servers

I have a Server Group with two servers; my "local" server (computer name)
and another "older" server that I was using for a particular purpose some
time ago. After doing an Uninstal/Reinstall the databases that WERE under
my "local" server are now attached to the other server! And the databases
from the older server are attached to my "local" server!
''?
TIA,
Larry WoodsDo you mean that the database file moved off to another machine and attached themselves to that
other machine? Or are you talking about instances? Perhaps there's some configuration in Client
Network Utility?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Larry Woods" <larry@.lwoods.com> wrote in message news:%23z3xmIEmDHA.3320@.tk2msftngp13.phx.gbl...
> I have a Server Group with two servers; my "local" server (computer name)
> and another "older" server that I was using for a particular purpose some
> time ago. After doing an Uninstal/Reinstall the databases that WERE under
> my "local" server are now attached to the other server! And the databases
> from the older server are attached to my "local" server!
> ''?
> TIA,
> Larry Woods
>|||Hi Larry,
Is this issue related to the problem in your previous post? If so, I would
like to gather and research them together. If I have misunderstood, please
feel free to let me know.
What is the versions of SQL Server (Local and Older), Service Pack? I
understand that there are two servers under the server group in the SQL
Server Enterprise Manager. I would like you to provide more information so
that I can narrow down this issue.
1. Is the "older" server named instance? Are the Local Server and Older
Server installed on the same machine?
2. What do you mean that "Uninstall/Reinstall" database? Do you mean
detach/attach database? Can you describe it in detail?
3. According to your description, I am not sure what your exact problem is.
Please feel free to let us know your accurate concerns.
Here is a useful article below:
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546.
I am standing by for your response.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Please read my response to myself.
Thanks.
Larry Woods
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ehno7ZGmDHA.1072@.TK2MSFTNGP09.phx.gbl...
> Do you mean that the database file moved off to another machine and
attached themselves to that
> other machine? Or are you talking about instances? Perhaps there's some
configuration in Client
> Network Utility?
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Larry Woods" <larry@.lwoods.com> wrote in message
news:%23z3xmIEmDHA.3320@.tk2msftngp13.phx.gbl...
> > I have a Server Group with two servers; my "local" server (computer
name)
> > and another "older" server that I was using for a particular purpose
some
> > time ago. After doing an Uninstal/Reinstall the databases that WERE
under
> > my "local" server are now attached to the other server! And the
databases
> > from the older server are attached to my "local" server!
> >
> > ''?
> >
> > TIA,
> >
> > Larry Woods
> >
> >
>|||I need to apologize for my ignorance. First, I DO have two servers in my
group. One of the servers is on another computer. When I reinstalled SQL
Server it looks like it included a "default" set of databases, "overwriting"
the databases that were in my default (local) SQL Server. I did find the
"old" databases in my Data folder so I guess that I have to reattached each
one individually, right? And, what I had mistaken for "copying" databases
was incorrect. The databases in the "foreign" server (the other computer)
were approximately the same ones as I had in my local server so I
misinterpretted what I saw.
Please verify that the reinstallation of SQL Server includes a default set
of databases. True? Also, does my explanation of what seems to have
happened make sense?
Thanks again.
Larry Woods
"Larry Woods" <larry@.lwoods.com> wrote in message
news:%23z3xmIEmDHA.3320@.tk2msftngp13.phx.gbl...
> I have a Server Group with two servers; my "local" server (computer name)
> and another "older" server that I was using for a particular purpose some
> time ago. After doing an Uninstal/Reinstall the databases that WERE under
> my "local" server are now attached to the other server! And the databases
> from the older server are attached to my "local" server!
> ''?
> TIA,
> Larry Woods
>|||Please read my response to myself.
Thanks.
Larry Woods
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:t6L%233TLmDHA.1408@.cpmsftngxa06.phx.gbl...
> Hi Larry,
> Is this issue related to the problem in your previous post? If so, I would
> like to gather and research them together. If I have misunderstood, please
> feel free to let me know.
> What is the versions of SQL Server (Local and Older), Service Pack? I
> understand that there are two servers under the server group in the SQL
> Server Enterprise Manager. I would like you to provide more information so
> that I can narrow down this issue.
> 1. Is the "older" server named instance? Are the Local Server and Older
> Server installed on the same machine?
> 2. What do you mean that "Uninstall/Reinstall" database? Do you mean
> detach/attach database? Can you describe it in detail?
> 3. According to your description, I am not sure what your exact problem
is.
> Please feel free to let us know your accurate concerns.
> Here is a useful article below:
> 314546 HOW TO: Move Databases Between Computers That Are Running SQL
Server
> http://support.microsoft.com/?id=314546.
> I am standing by for your response.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||Hi Larry,
Thanks for your feedback. According to your description, I apologize that I
am still not sure what the problem is. I think we need to make something
clear firstly.
1. What is the version of the both SQL Server (Service Pack)? Please review
[Item 1] to get the information about obtaining the version of SQL Server
(Service Pack).
2. You wrote "When I reinstalled SQL Serve", which Server you
"reinstalled"? Also you wrote: "One of the servers is on another computer".
Do you mean the "reinstall" indicate register SQL Server using SQL Server
Enterprise Manager?
For additional information regarding register SQL Server, please refer to
the following article on SQL Server Books Online.
Topic: "How to register a server (Enterprise Manager)"
Or you mean that you reinstall the SQL Server on the machine where the
local SQL Server located? Create a new instance or update the original
instance? If you create a new instance, you need to specify the reinstalled
SQL Server as named instance. Did you do it?
This step-by-step guide describes how to install a SQL Server 2000 basic
local installation.
303747 HOW TO: Install SQL Server 2000 - Basic Local Installation
http://support.microsoft.com/?id=303747
If I have misunderstood, please feel free to let me know and describe how
you reinstall the SQL Server.
Thank you for collecting the above information. It will definitely speed up
our progress. When we make the above things clear, we are able to
troubleshoot this problem more efficiently. Thanks for your understanding.
I am standing by for your response.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
[Item 1]
How to obtain the version of SQL Server (Service Pack)?
Please perform the following SQL statements using Query Analyzer.
select @.@.version
go
select serverproperty('productlevel')
go
For additional information regarding obtaining the version of SQL Server
(Service Pack), please refer to the following article on SQL Server Books
Online:
Topic: "@.@.VERSION"
Topic: "SERVERPROPERTY"|||Hi Larry,
Thanks for your feedback. Now, I still do not know the version of SQL
Server you want to install and the original SQL Server version. I assume
that you want to install MSDE 2000 on your computer which already has SQL
Server 2000. If I have misunderstood, please feel free to let me know.
For additional information regarding identifying the version of SQL Server,
please refer to the following article:
321185 HOW TO: Identify Your SQL Server Service Pack Version and Edition
http://support.microsoft.com/?id=321185
To install MSDE 2000 onto a machine, which already has SQL Server, we need
to make it clear that this new instance is only able to be installed as a
named instance.
I performed a test trying to install the MSDE 2000 on my machine, which
already has SQL Server 2000.
1. Download SQL2KDeskSP3 at the following URL:
Microsoft SQL Server 2000 Service Pack 3
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=9032
f608-160a-4537-a2b6-4cb265b80766
SQL2kdesksp3.exe includes all of the files that are required to install a
new instance of Desktop Engine (.msi files), to upgrade all existing
instances of Desktop Engine (.msp files), as well as to consume merge
modules (.msm files) into applications.
2. Configure setup options for MSDE 2.0 in the file Setup.ini.
-- Setup.ini --
[Options]
TARGETDIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Binn\"
DATADIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Data\"
INSTANCENAME="MyInstance"
SAPWD="sytest"
--
"sytest" is the password of the sa account. "MyInstance" is the name of the
instance.
For additional information regarding Customizing Desktop Engine Setup.exe,
please refer to the following article at SQL Server Books Online.
Topic: "Customizing Desktop Engine Setup.exe"
3. Double click Setup.exe to install MSDE 2.0 (named instance).
We can check to see MSSQL$ MYINSTANCE service is in the Services list. We
can also register the new named instance using <Computer Name>\MYINSTANCE
as the instance name via SQL Server Enterprise Manager.
It works on my side. Does it work on your side?
Also, I found some related articles below:
317328 HOW TO: Troubleshoot a SQL Server Desktop Engine 2000 Installation
and
http://support.microsoft.com/?id=317328
324998 HOW TO: Obtain and Install SQL Server 2000 Desktop Engine (MSDE 2000)
http://support.microsoft.com/?id=324998
814463 HOWTO: Specify a Strong SA Password When You Install SQL Server 2000
http://support.microsoft.com/?id=814463
Please feel free to post in the group if this solves your problem or if you
would like further assistance.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||I presently have SQL Server 2000 installed on my computer. I want to
install MSDE 2000. I will then be deploying MSDE 2000 with my application
at a later date. (Running XP Pro... The computer that will be receiving
MSDE will be running Win 2000 Server)
Thanks, again.
Larry
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:3eosgeSnDHA.2624@.cpmsftngxa06.phx.gbl...
> Hi Larry,
> Thanks for your feedback. Now, I still do not know the version of SQL
> Server you want to install and the original SQL Server version. I assume
> that you want to install MSDE 2000 on your computer which already has SQL
> Server 2000. If I have misunderstood, please feel free to let me know.
> For additional information regarding identifying the version of SQL
Server,
> please refer to the following article:
> 321185 HOW TO: Identify Your SQL Server Service Pack Version and Edition
> http://support.microsoft.com/?id=321185
>
> To install MSDE 2000 onto a machine, which already has SQL Server, we need
> to make it clear that this new instance is only able to be installed as a
> named instance.
> I performed a test trying to install the MSDE 2000 on my machine, which
> already has SQL Server 2000.
> 1. Download SQL2KDeskSP3 at the following URL:
> Microsoft SQL Server 2000 Service Pack 3
>
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=9032
> f608-160a-4537-a2b6-4cb265b80766
> SQL2kdesksp3.exe includes all of the files that are required to install a
> new instance of Desktop Engine (.msi files), to upgrade all existing
> instances of Desktop Engine (.msp files), as well as to consume merge
> modules (.msm files) into applications.
>
> 2. Configure setup options for MSDE 2.0 in the file Setup.ini.
> -- Setup.ini --
> [Options]
> TARGETDIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Binn\"
> DATADIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Data\"
> INSTANCENAME="MyInstance"
> SAPWD="sytest"
> --
> "sytest" is the password of the sa account. "MyInstance" is the name of
the
> instance.
> For additional information regarding Customizing Desktop Engine Setup.exe,
> please refer to the following article at SQL Server Books Online.
> Topic: "Customizing Desktop Engine Setup.exe"
> 3. Double click Setup.exe to install MSDE 2.0 (named instance).
> We can check to see MSSQL$ MYINSTANCE service is in the Services list. We
> can also register the new named instance using <Computer Name>\MYINSTANCE
> as the instance name via SQL Server Enterprise Manager.
> It works on my side. Does it work on your side?
> Also, I found some related articles below:
> 317328 HOW TO: Troubleshoot a SQL Server Desktop Engine 2000 Installation
> and
> http://support.microsoft.com/?id=317328
> 324998 HOW TO: Obtain and Install SQL Server 2000 Desktop Engine (MSDE
2000)
> http://support.microsoft.com/?id=324998
> 814463 HOWTO: Specify a Strong SA Password When You Install SQL Server
2000
> http://support.microsoft.com/?id=814463
> Please feel free to post in the group if this solves your problem or if
you
> would like further assistance.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||As far as downloading products, I have an MSDN Universal subscription. Are
all of these files on my CD's?
Larry
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:3eosgeSnDHA.2624@.cpmsftngxa06.phx.gbl...
> Hi Larry,
> Thanks for your feedback. Now, I still do not know the version of SQL
> Server you want to install and the original SQL Server version. I assume
> that you want to install MSDE 2000 on your computer which already has SQL
> Server 2000. If I have misunderstood, please feel free to let me know.
> For additional information regarding identifying the version of SQL
Server,
> please refer to the following article:
> 321185 HOW TO: Identify Your SQL Server Service Pack Version and Edition
> http://support.microsoft.com/?id=321185
>
> To install MSDE 2000 onto a machine, which already has SQL Server, we need
> to make it clear that this new instance is only able to be installed as a
> named instance.
> I performed a test trying to install the MSDE 2000 on my machine, which
> already has SQL Server 2000.
> 1. Download SQL2KDeskSP3 at the following URL:
> Microsoft SQL Server 2000 Service Pack 3
>
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=9032
> f608-160a-4537-a2b6-4cb265b80766
> SQL2kdesksp3.exe includes all of the files that are required to install a
> new instance of Desktop Engine (.msi files), to upgrade all existing
> instances of Desktop Engine (.msp files), as well as to consume merge
> modules (.msm files) into applications.
>
> 2. Configure setup options for MSDE 2.0 in the file Setup.ini.
> -- Setup.ini --
> [Options]
> TARGETDIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Binn\"
> DATADIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Data\"
> INSTANCENAME="MyInstance"
> SAPWD="sytest"
> --
> "sytest" is the password of the sa account. "MyInstance" is the name of
the
> instance.
> For additional information regarding Customizing Desktop Engine Setup.exe,
> please refer to the following article at SQL Server Books Online.
> Topic: "Customizing Desktop Engine Setup.exe"
> 3. Double click Setup.exe to install MSDE 2.0 (named instance).
> We can check to see MSSQL$ MYINSTANCE service is in the Services list. We
> can also register the new named instance using <Computer Name>\MYINSTANCE
> as the instance name via SQL Server Enterprise Manager.
> It works on my side. Does it work on your side?
> Also, I found some related articles below:
> 317328 HOW TO: Troubleshoot a SQL Server Desktop Engine 2000 Installation
> and
> http://support.microsoft.com/?id=317328
> 324998 HOW TO: Obtain and Install SQL Server 2000 Desktop Engine (MSDE
2000)
> http://support.microsoft.com/?id=324998
> 814463 HOWTO: Specify a Strong SA Password When You Install SQL Server
2000
> http://support.microsoft.com/?id=814463
> Please feel free to post in the group if this solves your problem or if
you
> would like further assistance.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||Hi Larry,
Thanks for your feedback.
Firstly I would like to make the following things clear in my previous post:
SQL2kdesksp3.exe includes a MSDE 2000 with SP3. This MSDE 2000 is installed
in my test in the previous post. It can be downloaded at following URL:
Microsoft SQL Server 2000 Service Pack 3
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=9032
f608-160a-4537-a2b6-4cb265b80766
I just installed a MSDE 2000 with SP3 in my test and did not only install
Service Pack 3. If you have any further concerns, please feel free to let
me know.
Then, I understand you installed SQL Server 2000 and two MSDE instances on
your machine. I am not sure if they are installed successfully only
according to the screen shot. Please check to see if the related services
are in the service list (Start-->Control Panel-->Administrative
Tools-->Services), such as MSSQLSERVER, MSSQL$<INSTANCE NAME>. In this
issue, there should be 3 services (MSSQLSERVER service, 2 MSSQL$<INSTANCE
NAME> services).
If these services are in the services list, please start these services and
try to register the related instances in the SQL Server Enterprise Manager.
For named instance, please use <Computer Name>\<Instance Name> to register.
After registering these three instances, please check to see if the
databases under these services are normal.
If the databases under the instance are abnormal or you cannot see the
above service in the service list, I would like you to provide the
sqldiag.txt file so that I can understand the system environment on your
side. For additional information regarding sqldiag utility, please review
[Item 1]. You can send it to me at v-yshao@.microsoft.com.
Also, if you only want to setup MSDE 2000 on the machine that already has
SQL Server 2000. You can uninstall these 2 MSDE from your machine and try
to install MSDE 2000 mentioned in my test in the previous post.
I am standing by for your response.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
[Item 1]
How to obtain the Sqldiag.txt file
Please provide the Sqldiag.txt (by default located in \Mssql\Log) using
Sqldiag utility (Sqldiag.exe by default located in C:\Program
Files\Microsoft SQL Server\MSSQL\Binn). If you are unable to find the
Sqldiag.exe, please search the Sqldiag.exe file and run this utility. Then
please search the Sqldiag.txt file and provide it to me.|||Michael,
This is an important project for me but at the present time XP Pro is
"eating" my disk (6 Gig to 0 in less thatn 1 day--no reason!) and I am going
to be forced into reverting back to Windows 2000. This means rebuilding TWO
systems so I will be busy for a few days. I DEFINITELY will get back to
this as soon as I get rid of this "latest and greatest" of MS's operating
systems!!!!
Larry
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:sdCKEEunDHA.1548@.cpmsftngxa06.phx.gbl...
> Hi Larry,
> Thanks for your feedback.
> Firstly I would like to make the following things clear in my previous
post:
> SQL2kdesksp3.exe includes a MSDE 2000 with SP3. This MSDE 2000 is
installed
> in my test in the previous post. It can be downloaded at following URL:
> Microsoft SQL Server 2000 Service Pack 3
>
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=9032
> f608-160a-4537-a2b6-4cb265b80766
> I just installed a MSDE 2000 with SP3 in my test and did not only install
> Service Pack 3. If you have any further concerns, please feel free to let
> me know.
> Then, I understand you installed SQL Server 2000 and two MSDE instances on
> your machine. I am not sure if they are installed successfully only
> according to the screen shot. Please check to see if the related services
> are in the service list (Start-->Control Panel-->Administrative
> Tools-->Services), such as MSSQLSERVER, MSSQL$<INSTANCE NAME>. In this
> issue, there should be 3 services (MSSQLSERVER service, 2 MSSQL$<INSTANCE
> NAME> services).
> If these services are in the services list, please start these services
and
> try to register the related instances in the SQL Server Enterprise
Manager.
> For named instance, please use <Computer Name>\<Instance Name> to
register.
> After registering these three instances, please check to see if the
> databases under these services are normal.
> If the databases under the instance are abnormal or you cannot see the
> above service in the service list, I would like you to provide the
> sqldiag.txt file so that I can understand the system environment on your
> side. For additional information regarding sqldiag utility, please review
> [Item 1]. You can send it to me at v-yshao@.microsoft.com.
> Also, if you only want to setup MSDE 2000 on the machine that already has
> SQL Server 2000. You can uninstall these 2 MSDE from your machine and try
> to install MSDE 2000 mentioned in my test in the previous post.
> I am standing by for your response.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> [Item 1]
> How to obtain the Sqldiag.txt file
> Please provide the Sqldiag.txt (by default located in \Mssql\Log) using
> Sqldiag utility (Sqldiag.exe by default located in C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn). If you are unable to find the
> Sqldiag.exe, please search the Sqldiag.exe file and run this utility. Then
> please search the Sqldiag.txt file and provide it to me.
>|||Hi Larry,
Thanks for your feedback. Your patience is appreciated.
For the problem with XP pro "eating" the disk, I would like you to check
the size of this folder (C:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP). This folder usually contained all the SQL Server
backup files. According to your description, I suspected there are some
backup jobs performing on the background, which created the backup files
"eating" the disk. Does it resolve your problem?
If not, please check to see if there is worm virus on your computer.
Also, did you try my suggestions on your machine? I am standing by for your
response.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||I don't think there is ANY connection between SQL Server and the loss of
disk space...but maybe there is. In any case, I threw in the towel and
rebuilt the system with Win 2000. I now have a SQL Server Group with two
servers: (local) and DEVELOPMENT\VSdotNET. DEVELOPMENT is the name of my
computer. When I checked the Properties of the "VSdotNET" server I see that
it is MSDE. Does all of this sound right?
Larry
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:NAo8JWxnDHA.2148@.cpmsftngxa06.phx.gbl...
> Hi Larry,
> Thanks for your feedback. Your patience is appreciated.
> For the problem with XP pro "eating" the disk, I would like you to check
> the size of this folder (C:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP). This folder usually contained all the SQL Server
> backup files. According to your description, I suspected there are some
> backup jobs performing on the background, which created the backup files
> "eating" the disk. Does it resolve your problem?
> If not, please check to see if there is worm virus on your computer.
> Also, did you try my suggestions on your machine? I am standing by for
your
> response.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||Hi Larry,
Thanks for your feedback. It seems that you have rebuilt the system with
Win 2000 and the Windows XP has been removed. I understand that there are
two instances (Local and DEVELOPMENT\VSdotNET) in the SQL Server Group
using SQL Server Enterprise Manager. The DEVELOPMENT\VSdotNET instance's
version is MSDE. If I have misunderstood, please feel free to let me know.
Everything seems worked fine. According to your above description, I am
unable to find something abnormal. Currently, does any problem occur on
your side?
Please feel free to post it in the group if you need further assistance.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.sql