| Author |
Topic |
|
kirkeby
Yak Posting Veteran
57 Posts |
 Posted - 2003-05-14 : 09:38:15
|
| Hi! I need some help because I cannot find the answers I need. We have a new installation of SQL Server 2000 with a default instance. We also have some Quest software that cannot talk to the database it needs because the instance is not named. It has to have a named instance in order to talk (!) to the database. I know you cannot rename an instance. I am trying to find the least painful way to rememdy this situation. I could reinstall SQL Server or I could install a new instance of SQL Server. Do you have to have a default instance or can you have only one instance that is named? Sorry for all of the questions but I'm new to SQL Server 2000 and am having to learn fast.If I install a new instance of SQL Server 2000, can the instance access the databases under the default instance? If it can, then no one would be directly accessing the default instance...it would merely be housing the databases, etc.. Are there problems with this approach (if do-able)?I am trying to avoid having to move all databases, stored procedures, logins, etc. to the new instance and really trying to avoid reinstalling altogether as we are already in production.Is there a better way that you would recommend?Thank you for your help! I need to figure out the solution quick and get it implemented within the next 2-3 days.Lisa KirkebyBPkirkeblm@bp.comSQL 7.0 SP3, NT 4.0 (1381), CP 1252 |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-05-14 : 10:12:43
|
| I believe the default instance is just the name of the server, like sql 7. I've run in to this because old sql 7 odbc drivers can talk to the default instance of sql2k, but not a named instance.Which Quest product are you using?You probably could contact their help desk support to resolve your problem...should not be too big of an issue.Brett8-)Edited by - x002548 on 05/14/2003 10:27:34 |
 |
|
|
kirkeby
Yak Posting Veteran
57 Posts |
Posted - 2003-05-14 : 10:25:25
|
| I'm trying to find out which Quest product it is and, once I do, will contact them. The instance name is not the same as the server name. If you run "select serverproperty('ServerName'), serverproperty('MachineName'), serverproperty('InstanceName')" it returns:server name = va1houii002machine name = va1houii002instance name = NULLLisa KirkebyBPkirkeblm@bp.comSQL 7.0 SP3, NT 4.0 (1381), CP 1252 |
|
|
|
kirkeby
Yak Posting Veteran
57 Posts |
Posted - 2003-05-14 : 11:10:33
|
| Could someone please tell me if 2 instances on a SQL 2000 server can share everything, databases, stored procedures, etc.? Thank you!Lisa KirkebyBPkirkeblm@bp.comSQL 7.0 SP3, NT 4.0 (1381), CP 1252 |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2003-05-14 : 11:38:52
|
quote:
Could someone please tell me if 2 instances on a SQL 2000 server can share everything, databases, stored procedures, etc.? Thank you!Lisa KirkebyBPkirkeblm@bp.comSQL 7.0 SP3, NT 4.0 (1381), CP 1252
No, they can't share any of that stuff.Jay White{0} |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-05-14 : 12:52:53
|
| You can get to the other instances objects using linked servers but not shareable.Tara |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-05-14 : 13:22:06
|
| Well, isn't that the cool thing about SQL2k? The instances are isolated, so that if one instance fails the other is unaffected (at least that the theory).Brett8-) |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-05-14 : 13:26:09
|
| Yep that's what I thought too! There are a few things shared between the instances (some installation files), but none are database objects.Tara |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-05-15 : 16:37:37
|
| Lisa,Did you ever get it resolved?Brett8-) |
|
|
|
kirkeby
Yak Posting Veteran
57 Posts |
Posted - 2003-05-19 : 08:51:49
|
| Fortunately, we will not have to reinstall SQL or do anything on the SQL side, for that matter. I finally found out what Quest tool it was (password reset) and had someone contact them because I became convinced it was a configuration issue on the Quest side. And I was right. There is more than one way to connect to the database with Quest and the people configuring it simply did not have enough information to know to do it. Thank you, everyone, for your timely input! This is the best place to go if you cannot find the answer to your questions! :-)Lisa KirkebyBPkirkeblm@bp.comSQL 7.0 SP3, NT 4.0 (1381), CP 1252 |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-05-20 : 01:24:18
|
| You can install a single named instance without a default instance. Only Client tools are shared.-Chadhttp://www.clrsoft.comSoftware built for the Common Language Runtime. |
|
|
|
|
Instance questions