vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have several database on a Windows Server 2003. I re-registered this SQL server, which is local, and after that I cannot see any of the databases in the Enterprise Manager. The databases still work, since my applications work fine. I have no clue how can I make these databases visible in Enterprise Manager. I tried registering this SQL Server in Enterprise Manager under Windows accounts and SQL Server accounts. Nothing works. Can anybody help? |
| |||
| df (df@df.com) writes: > I have several database on a Windows Server 2003. I re-registered this > SQL server, which is local, and after that I cannot see any of the > databases in the Enterprise Manager. The databases still work, since my > applications work fine. I have no clue how can I make these databases > visible in Enterprise Manager. I tried registering this SQL Server in > Enterprise Manager under Windows accounts and SQL Server accounts. I have no idea, but my guess is that you registered as a user that does not have permission to these databases, and not as a user that has admin priviledges. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp |
| |||
| df wrote: > I have several database on a Windows Server 2003. I re-registered this SQL > server, which is local, and after that I cannot see any of the databases in > the Enterprise Manager. The databases still work, since my applications work > fine. I have no clue how can I make these databases visible in Enterprise > Manager. I tried registering this SQL Server in Enterprise Manager under > Windows accounts and SQL Server accounts. Nothing works. > Can anybody help? The account you use in Enterprse Manager probably has no admin permission. Did you try "sa"? If your SQL Server doesn't allow SQL login you need to RTFM and enable it. |
| |||
| Tried "sa", the same story. Tried Windows auth., no diff. Only default databases are visible. "Aquila Deus" <aquila.deus@gmail.com> wrote in message news:1112170808.553461.149460@f14g2000cwb.googlegr oups.com... > df wrote: >> I have several database on a Windows Server 2003. I re-registered > this SQL >> server, which is local, and after that I cannot see any of the > databases in >> the Enterprise Manager. The databases still work, since my > applications work >> fine. I have no clue how can I make these databases visible in > Enterprise >> Manager. I tried registering this SQL Server in Enterprise Manager > under >> Windows accounts and SQL Server accounts. Nothing works. >> Can anybody help? > > The account you use in Enterprse Manager probably has no admin > permission. Did you try "sa"? If your SQL Server doesn't allow SQL > login you need to RTFM and enable it. > |
| |||
| When I looked in the Windows services I see another instance of SQL Server running. There are the following services: MSSQL$DELLSRV MSSqlSever I have no clue how this could happen. But the question is how can I get to the old instance??? "Aquila Deus" <aquila.deus@gmail.com> wrote in message news:1112170808.553461.149460@f14g2000cwb.googlegr oups.com... > df wrote: >> I have several database on a Windows Server 2003. I re-registered > this SQL >> server, which is local, and after that I cannot see any of the > databases in >> the Enterprise Manager. The databases still work, since my > applications work >> fine. I have no clue how can I make these databases visible in > Enterprise >> Manager. I tried registering this SQL Server in Enterprise Manager > under >> Windows accounts and SQL Server accounts. Nothing works. >> Can anybody help? > > The account you use in Enterprse Manager probably has no admin > permission. Did you try "sa"? If your SQL Server doesn't allow SQL > login you need to RTFM and enable it. > |
| |||
| df wrote: > When I looked in the Windows services I see another instance of SQL Server > running. There are the following services: > MSSQL$DELLSRV > MSSqlSever > > I have no clue how this could happen. But the question is how can I get to > the old instance??? Depends on the network interface you configured for the two instances. The default share memory is exclusive and can't be used by both (and you may not be able to know who uses it exactly), so I suggest you to enable named pipe for them, and re-register them in Enterprise Manager by the named pipe path you set. |
| |||
| df (df@df.com) writes: > When I looked in the Windows services I see another instance of SQL Server > running. There are the following services: > MSSQL$DELLSRV > MSSqlSever > > I have no clue how this could happen. But the question is how can I get to > the old instance??? So you have two instances of SQL Server on your machine, and you have connected to the one that does not have any databases. To connect to the default instance, specify "." or servername. To connect to the other, specify ".\DELLSRV" or "servername\DELLSRV". You might also want to check the Client Network Utility whether you have any aliases. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp |
| |||
| Thanks, I have fixed the problem. I suspect that when I installed service packs, it created the second instance, since I did not do it explicitly. I shut it down, and registered the original one. "Erland Sommarskog" <esquel@sommarskog.se> wrote in message news:Xns9629EB819DA24Yazorman@127.0.0.1... > df (df@df.com) writes: >> When I looked in the Windows services I see another instance of SQL >> Server >> running. There are the following services: >> MSSQL$DELLSRV >> MSSqlSever >> >> I have no clue how this could happen. But the question is how can I get >> to >> the old instance??? > > So you have two instances of SQL Server on your machine, and you have > connected to the one that does not have any databases. > > To connect to the default instance, specify "." or servername. To > connect to the other, specify ".\DELLSRV" or "servername\DELLSRV". > > You might also want to check the Client Network Utility whether you > have any aliases. > > > -- > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se > > Books Online for SQL Server SP3 at > http://www.microsoft.com/sql/techinf...2000/books.asp |
| |||
| df (df@df.com) writes: > I have fixed the problem. I suspect that when I installed service packs, > it created the second instance, since I did not do it explicitly. I shut > it down, and registered the original one. I don't know which of the instances was the unexpected one, but it could be an MSDE instance that slipped in with some 3rd party software. DELLSRV hints a certain vendor. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server SP3 at http://www.microsoft.com/sql/techinf...2000/books.asp |
| ||||
| DELLSRV is my server name, I named it this way, no mistery here, it's DELL server. "Erland Sommarskog" <esquel@sommarskog.se> wrote in message news:Xns962A5F6E379A3Yazorman@127.0.0.1... > df (df@df.com) writes: > > I have fixed the problem. I suspect that when I installed service packs, > > it created the second instance, since I did not do it explicitly. I shut > > it down, and registered the original one. > > I don't know which of the instances was the unexpected one, but it > could be an MSDE instance that slipped in with some 3rd party software. > DELLSRV hints a certain vendor. > > > -- > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se > > Books Online for SQL Server SP3 at > http://www.microsoft.com/sql/techinf...2000/books.asp |