Does Sql Server 2005 Installation create a default instance?

Hello everybody!

I have recently installed Sql Server 2005 Enterprise Edition on my PC and I have noticed that it has not installed a default instance. I have tried to do this several times even in some other PC but no default instance is installed.

I can get a default instance if I install Sql Server 2000 but this is not the same I guess. Is there any way to install the default instance via Sql Server 2005?

Do you have already a SQL Server instance installed on the system ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Are u able to install Named Instance? if not Check the OS. Enterprise Edition need Server Version of OS. Otherwise u can only install client component.

Madhu

|||Well, as I mentioned before I have installed Sql Server 2005 in several computers but I can explain you some of the cases:
1. In my computer I had already installed Sql Server 2000 and I had created two other instances except the default instance (LOCAL). Then I installed Sql Server 2005.
As a matter of fact I want to make a web synchronization for a merge replication. But I can not configure the merge replication for web synchronization because the database and its instance seems to be in SQL server 2000. That's why I want an 2005 sql server instance.

2. I have also uninstalled Sql Server 2000 and all of its instances from my computer, and I have reinstalled Sql Server 2005. But no default instance was created.

3. I have also installes Sql Server 2005 in another PC which had no instace installed, but the results were the same.

What should I do?

|||Do you mean I can not create any instance if my OS is Windows XP?
|||

Yes if you are installing Enterprise Edition it will not install Services on Windows XP. You can install Standard or any other Edition

http://www.microsoft.com/sql/editions/enterprise/sysreqs.mspx

Madhu

|||Thank U

Does Sql Server 2005 Installation create a default instance?

Hello everybody!

I have recently installed Sql Server 2005 Enterprise Edition on my PC and I have noticed that it has not installed a default instance. I have tried to do this several times even in some other PC but no default instance is installed.

I can get a default instance if I install Sql Server 2000 but this is not the same I guess. Is there any way to install the default instance via Sql Server 2005?

Do you have already a SQL Server instance installed on the system ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Are u able to install Named Instance? if not Check the OS. Enterprise Edition need Server Version of OS. Otherwise u can only install client component.

Madhu

|||Well, as I mentioned before I have installed Sql Server 2005 in several computers but I can explain you some of the cases:
1. In my computer I had already installed Sql Server 2000 and I had created two other instances except the default instance (LOCAL). Then I installed Sql Server 2005.
As a matter of fact I want to make a web synchronization for a merge replication. But I can not configure the merge replication for web synchronization because the database and its instance seems to be in SQL server 2000. That's why I want an 2005 sql server instance.

2. I have also uninstalled Sql Server 2000 and all of its instances from my computer, and I have reinstalled Sql Server 2005. But no default instance was created.

3. I have also installes Sql Server 2005 in another PC which had no instace installed, but the results were the same.

What should I do?

|||Do you mean I can not create any instance if my OS is Windows XP?
|||

Yes if you are installing Enterprise Edition it will not install Services on Windows XP. You can install Standard or any other Edition

http://www.microsoft.com/sql/editions/enterprise/sysreqs.mspx

Madhu

|||Thank U

Does Sql Server 2005 Installation create a default instance?

Hello everybody!

I have recently installed Sql Server 2005 Enterprise Edition on my PC and I have noticed that it has not installed a default instance. I have tried to do this several times even in some other PC but no default instance is installed.

I can get a default instance if I install Sql Server 2000 but this is not the same I guess. Is there any way to install the default instance via Sql Server 2005?

Do you have already a SQL Server instance installed on the system ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Are u able to install Named Instance? if not Check the OS. Enterprise Edition need Server Version of OS. Otherwise u can only install client component.

Madhu

|||Well, as I mentioned before I have installed Sql Server 2005 in several computers but I can explain you some of the cases:
1. In my computer I had already installed Sql Server 2000 and I had created two other instances except the default instance (LOCAL). Then I installed Sql Server 2005.
As a matter of fact I want to make a web synchronization for a merge replication. But I can not configure the merge replication for web synchronization because the database and its instance seems to be in SQL server 2000. That's why I want an 2005 sql server instance.

2. I have also uninstalled Sql Server 2000 and all of its instances from my computer, and I have reinstalled Sql Server 2005. But no default instance was created.

3. I have also installes Sql Server 2005 in another PC which had no instace installed, but the results were the same.

What should I do?

|||Do you mean I can not create any instance if my OS is Windows XP?
|||

Yes if you are installing Enterprise Edition it will not install Services on Windows XP. You can install Standard or any other Edition

http://www.microsoft.com/sql/editions/enterprise/sysreqs.mspx

Madhu

|||Thank U
sql

Does Sql Server 2005 Enterprise Edition Support Managed Code ?

Dear friends,

please help,

let me tell you what happens,

1) first i installed Sql Server 2005 Enterprise Edition, everything was working fine except i was not able to create managed objects from BI, like stored procedures, triggers, UDT, etc etc.

2) so i installed VS.net 2005 complete + Sql Server 2005 Express Edition

now i was able to create stored procedures, triggers, etc etc, i'm talking about the CLR objects, ok, i.e. the managed code, but........ i was only able to do this from Sql Server 2005 Express Edition.

whenever i try to create managed objects CLR like stored procedures and stuff from the Sql Server 2005 Enterprise edition it gives me the following error :

"The Sql Server supplied by these connection properties, does not support managed code, please choose a different server"

please help meeeee.. please please, tell me what's the problem ?

below i'm attaching a screenshot of the error....

first off, I ASSURE you SQL Server 2005 EE supports SQLCLR. http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

secondly, sql server 2005 has CLR Integration turned off by default and if you were to attempt using a sql 2005 EE default install/instance you could still deploy the sqlclr routines, its just that upon attempting to use them you would receive the error "Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option."

I can only reason that you are in fact NOT connecting to a SQL Server 2005 instance from a Visual Studio 2005 database project.

|||

yes even i think i was using, sql server 2000 your right.

thanks for your kind help,

regards,

Gurjit Singh

sql

Does SQL Server 2000 Standard Edition does not support SAN ?

Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
protocols by using the Virtual Interface Architecture (VIA), but it doesn't
say explicitly : whether SQL Server 2000 Standard Edition also supports VIA.
So I don't know do I have to buy the Enterprise Edition if I want to use SAN
as the storage area for my SQL 2000 application.
Can anybody help me on it because the Enterprise Edition is much expensive
than the Standard Edition.No, Standard edition does not support SAN. Check
http://www.microsoft.com/sql/evaluation/features/choosing.asp.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c7kl9m$1i61212@.imsp212.netvigator.com...
> Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
> protocols by using the Virtual Interface Architecture (VIA), but it
doesn't
> say explicitly : whether SQL Server 2000 Standard Edition also supports
VIA.
> So I don't know do I have to buy the Enterprise Edition if I want to use
SAN
> as the storage area for my SQL 2000 application.
> Can anybody help me on it because the Enterprise Edition is much expensive
> than the Standard Edition.
>|||To add to Dejan's response, the SAN acronym has 2 completely different
meanings depending on the context. SAN can refer to a Storage Area Network
or a System Area Network. All editions of SQL Server support Storage Area
Networks, which is a common data storage technology. You don't need
Enterprise Edition for this.
However, SQL Server Enterprise Edition is needed to support System Area
Network, which provides a high-speed network communication between different
servers.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c7kl9m$1i61212@.imsp212.netvigator.com...
> Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
> protocols by using the Virtual Interface Architecture (VIA), but it
doesn't
> say explicitly : whether SQL Server 2000 Standard Edition also supports
VIA.
> So I don't know do I have to buy the Enterprise Edition if I want to use
SAN
> as the storage area for my SQL 2000 application.
> Can anybody help me on it because the Enterprise Edition is much expensive
> than the Standard Edition.
>|||Thanks for your reply.
I mean 'Storage Area Network'.
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:ejil$OdNEHA.3052@.TK2MSFTNGP12.phx.gbl...
> To add to Dejan's response, the SAN acronym has 2 completely different
> meanings depending on the context. SAN can refer to a Storage Area
Network
> or a System Area Network. All editions of SQL Server support Storage Area
> Networks, which is a common data storage technology. You don't need
> Enterprise Edition for this.
> However, SQL Server Enterprise Edition is needed to support System Area
> Network, which provides a high-speed network communication between
different
> servers.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c7kl9m$1i61212@.imsp212.netvigator.com...
> > Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
> > protocols by using the Virtual Interface Architecture (VIA), but it
> doesn't
> > say explicitly : whether SQL Server 2000 Standard Edition also supports
> VIA.
> > So I don't know do I have to buy the Enterprise Edition if I want to use
> SAN
> > as the storage area for my SQL 2000 application.
> > Can anybody help me on it because the Enterprise Edition is much
expensive
> > than the Standard Edition.
> >
> >
>

Does SQL Server 2000 Standard Edition does not support SAN ?

Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
protocols by using the Virtual Interface Architecture (VIA), but it doesn't
say explicitly : whether SQL Server 2000 Standard Edition also supports VIA.
So I don't know do I have to buy the Enterprise Edition if I want to use SAN
as the storage area for my SQL 2000 application.
Can anybody help me on it because the Enterprise Edition is much expensive
than the Standard Edition.
No, Standard edition does not support SAN. Check
http://www.microsoft.com/sql/evaluat.../choosing.asp.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c7kl9m$1i61212@.imsp212.netvigator.com...
> Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
> protocols by using the Virtual Interface Architecture (VIA), but it
doesn't
> say explicitly : whether SQL Server 2000 Standard Edition also supports
VIA.
> So I don't know do I have to buy the Enterprise Edition if I want to use
SAN
> as the storage area for my SQL 2000 application.
> Can anybody help me on it because the Enterprise Edition is much expensive
> than the Standard Edition.
>
|||To add to Dejan's response, the SAN acronym has 2 completely different
meanings depending on the context. SAN can refer to a Storage Area Network
or a System Area Network. All editions of SQL Server support Storage Area
Networks, which is a common data storage technology. You don't need
Enterprise Edition for this.
However, SQL Server Enterprise Edition is needed to support System Area
Network, which provides a high-speed network communication between different
servers.
Hope this helps.
Dan Guzman
SQL Server MVP
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c7kl9m$1i61212@.imsp212.netvigator.com...
> Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
> protocols by using the Virtual Interface Architecture (VIA), but it
doesn't
> say explicitly : whether SQL Server 2000 Standard Edition also supports
VIA.
> So I don't know do I have to buy the Enterprise Edition if I want to use
SAN
> as the storage area for my SQL 2000 application.
> Can anybody help me on it because the Enterprise Edition is much expensive
> than the Standard Edition.
>
|||Thanks for your reply.
I mean 'Storage Area Network'.
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:ejil$OdNEHA.3052@.TK2MSFTNGP12.phx.gbl...
> To add to Dejan's response, the SAN acronym has 2 completely different
> meanings depending on the context. SAN can refer to a Storage Area
Network
> or a System Area Network. All editions of SQL Server support Storage Area
> Networks, which is a common data storage technology. You don't need
> Enterprise Edition for this.
> However, SQL Server Enterprise Edition is needed to support System Area
> Network, which provides a high-speed network communication between
different[vbcol=seagreen]
> servers.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c7kl9m$1i61212@.imsp212.netvigator.com...
> doesn't
> VIA.
> SAN
expensive
>
sql

Does SQL Server 2000 Standard Edition does not support SAN ?

Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
protocols by using the Virtual Interface Architecture (VIA), but it doesn't
say explicitly : whether SQL Server 2000 Standard Edition also supports VIA.
So I don't know do I have to buy the Enterprise Edition if I want to use SAN
as the storage area for my SQL 2000 application.
Can anybody help me on it because the Enterprise Edition is much expensive
than the Standard Edition.No, Standard edition does not support SAN. Check
http://www.microsoft.com/sql/evalua...s/choosing.asp.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c7kl9m$1i61212@.imsp212.netvigator.com...
> Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
> protocols by using the Virtual Interface Architecture (VIA), but it
doesn't
> say explicitly : whether SQL Server 2000 Standard Edition also supports
VIA.
> So I don't know do I have to buy the Enterprise Edition if I want to use
SAN
> as the storage area for my SQL 2000 application.
> Can anybody help me on it because the Enterprise Edition is much expensive
> than the Standard Edition.
>|||To add to Dejan's response, the SAN acronym has 2 completely different
meanings depending on the context. SAN can refer to a Storage Area Network
or a System Area Network. All editions of SQL Server support Storage Area
Networks, which is a common data storage technology. You don't need
Enterprise Edition for this.
However, SQL Server Enterprise Edition is needed to support System Area
Network, which provides a high-speed network communication between different
servers.
Hope this helps.
Dan Guzman
SQL Server MVP
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c7kl9m$1i61212@.imsp212.netvigator.com...
> Microsoft web site says SQL Server 2000 Enterprise Edition supports SAN
> protocols by using the Virtual Interface Architecture (VIA), but it
doesn't
> say explicitly : whether SQL Server 2000 Standard Edition also supports
VIA.
> So I don't know do I have to buy the Enterprise Edition if I want to use
SAN
> as the storage area for my SQL 2000 application.
> Can anybody help me on it because the Enterprise Edition is much expensive
> than the Standard Edition.
>|||Thanks for your reply.
I mean 'Storage Area Network'.
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:ejil$OdNEHA.3052@.TK2MSFTNGP12.phx.gbl...
> To add to Dejan's response, the SAN acronym has 2 completely different
> meanings depending on the context. SAN can refer to a Storage Area
Network
> or a System Area Network. All editions of SQL Server support Storage Area
> Networks, which is a common data storage technology. You don't need
> Enterprise Edition for this.
> However, SQL Server Enterprise Edition is needed to support System Area
> Network, which provides a high-speed network communication between
different
> servers.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c7kl9m$1i61212@.imsp212.netvigator.com...
> doesn't
> VIA.
> SAN
expensive[vbcol=seagreen]
>

Does not connect with Enterprise Manger

I am not been able to connect to SQL Server with Enterprise Manger as I
increased the number of databases upto 170 .Earlier i had no problem when I
had less of databases .Moreover there is no problem in connecting through
Query Analyser.
Could any one help please ?
Regards
Musharraf SultanHi,
Are you getting any errors or any timeouts? Can you try the
enterperisemanager from the SQL server machine and see as well.
Thanks
Hari
SQL Server MVP
"NEWS" <musharrafs@.yahoo.com> wrote in message
news:eM$2fOlzGHA.4228@.TK2MSFTNGP06.phx.gbl...
>I am not been able to connect to SQL Server with Enterprise Manger as I
>increased the number of databases upto 170 .Earlier i had no problem when I
>had less of databases .Moreover there is no problem in connecting through
>Query Analyser.
> Could any one help please ?
> Regards
> Musharraf Sultan
>
>|||Thanks a lot ...
As soon as I try to connect from Enterprise Manager an Hourglass appears
and after some time if I see from Task manager
it shows NOT RESPONDING. The same thing happens on the Server as well as
from remote machines
Regards
Musharraf
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ebZ7GopzGHA.4920@.TK2MSFTNGP06.phx.gbl...
> Hi,
> Are you getting any errors or any timeouts? Can you try the
> enterperisemanager from the SQL server machine and see as well.
> Thanks
> Hari
> SQL Server MVP
> "NEWS" <musharrafs@.yahoo.com> wrote in message
> news:eM$2fOlzGHA.4228@.TK2MSFTNGP06.phx.gbl...
>|||Hi,
See the database option Autoclose is enabled. If yes use the SP_DBOPTION to
make the Autoclose disabled for all database.
Thanks
Hari
SQL Server MVP
"NEWS" <musharrafs@.yahoo.com> wrote in message
news:ePChVYB0GHA.2072@.TK2MSFTNGP06.phx.gbl...
> Thanks a lot ...
> As soon as I try to connect from Enterprise Manager an Hourglass appears
> and after some time if I see from Task manager
> it shows NOT RESPONDING. The same thing happens on the Server as well as
> from remote machines
> Regards
> Musharraf
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:ebZ7GopzGHA.4920@.TK2MSFTNGP06.phx.gbl...
>

Does AWE is needed ?

I have a server with Windows server 2003 enterprise edition, 6gb ram.
(32bit)
I installed SQL 2000 with SP4 on it, i configured it to use only 5gb of
memory.
Do i have to enable AWE for this box or this is enough for optimal
performance ?
my server show in the boot.ini "/PAE"
Thanks,,,Hi
http://support.microsoft.com/kb/274750
Aslo , read about hotfix
http://support.microsoft.com/kb/899761
"Mahmoud Amin" <mm.amin@.gmail.com> wrote in message
news:eE0c1aZYIHA.1212@.TK2MSFTNGP05.phx.gbl...
>I have a server with Windows server 2003 enterprise edition, 6gb ram.
>(32bit)
> I installed SQL 2000 with SP4 on it, i configured it to use only 5gb of
> memory.
> Do i have to enable AWE for this box or this is enough for optimal
> performance ?
> my server show in the boot.ini "/PAE"
> Thanks,,,
>

Documenting Tables

Is there a way to document what a tables does within Enterprise Manager? I'm
thinking no, so my next question is what is the best way to describe what a
table is used for...aside from a descriptive name. Thanks.Mike Collins wrote:
> Is there a way to document what a tables does within Enterprise
> Manager? I'm thinking no, so my next question is what is the best way
> to describe what a table is used for...aside from a descriptive name.
> Thanks.
In your database design document and logical model. You can add descriptive
information to database objects using sp_addextendedproperty
David Gugick
Quest Software|||Thanks...I also found out that you can use Query Analyzer to add/delete
extended properties.
"David Gugick" wrote:
> Mike Collins wrote:
> > Is there a way to document what a tables does within Enterprise
> > Manager? I'm thinking no, so my next question is what is the best way
> > to describe what a table is used for...aside from a descriptive name.
> > Thanks.
> In your database design document and logical model. You can add descriptive
> information to database objects using sp_addextendedproperty
>
> --
> David Gugick
> Quest Software
>
>

Documenting Tables

Is there a way to document what a tables does within Enterprise Manager? I'm
thinking no, so my next question is what is the best way to describe what a
table is used for...aside from a descriptive name. Thanks.
Mike Collins wrote:
> Is there a way to document what a tables does within Enterprise
> Manager? I'm thinking no, so my next question is what is the best way
> to describe what a table is used for...aside from a descriptive name.
> Thanks.
In your database design document and logical model. You can add descriptive
information to database objects using sp_addextendedproperty
David Gugick
Quest Software
|||Thanks...I also found out that you can use Query Analyzer to add/delete
extended properties.
"David Gugick" wrote:

> Mike Collins wrote:
> In your database design document and logical model. You can add descriptive
> information to database objects using sp_addextendedproperty
>
> --
> David Gugick
> Quest Software
>
>

Documenting Tables

Is there a way to document what a tables does within Enterprise Manager? I'm
thinking no, so my next question is what is the best way to describe what a
table is used for...aside from a descriptive name. Thanks.Mike Collins wrote:
> Is there a way to document what a tables does within Enterprise
> Manager? I'm thinking no, so my next question is what is the best way
> to describe what a table is used for...aside from a descriptive name.
> Thanks.
In your database design document and logical model. You can add descriptive
information to database objects using sp_addextendedproperty
David Gugick
Quest Software|||Thanks...I also found out that you can use Query Analyzer to add/delete
extended properties.
"David Gugick" wrote:

> Mike Collins wrote:
> In your database design document and logical model. You can add descriptiv
e
> information to database objects using sp_addextendedproperty
>
> --
> David Gugick
> Quest Software
>
>

Document for In-Place Upgrade of SQL Server 2000 to 2005

Hi,

We are performing the In-Place upgrade of SQL Server 2000(enterprise) to 2005(enterprise) in a clustered environment.

The issue is that the upgrade does not proceed in case both the machines in the cluster are running.

The error shown is

Product Name : Microsoft SQL Server
Product Version : 9.00.1399.06
Message Source : setup.rll
Message ID : 50000
EvtType : datastore\clustergroupsproperties.cpp@.InvokeSqlSetupDllAction@.ClusterGroupScope.SharedDisks@.0x2

It proceeds (with some errors) only if i stop the cluster service on the other machine. It is an expected behavior?

Does anyone have the documentation for this type of upgrade? Or just the basic steps to be followed.

http://www.sqlservercentral.com/columnists/ssamuel/2987.asp

http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en

check these links might be helpful

|||

In virtually every case of a cluster upgrade, I always tell my clients to perform a new install and not perform an in-place upgrade. If you have this option, take it. Upgrading in place is possible, but fraught with difficulties.

|||

I would need more information on your configuration and the exact steps you are going through. I wrote the section in the upgrade documentation for upgrading a cluster. I've upgraded both single instance and multi-instance clusters, in place, without any of the issues you are mentioning.

Document for In-Place Upgrade of SQL Server 2000 to 2005

Hi,

We are performing the In-Place upgrade of SQL Server 2000(enterprise) to 2005(enterprise) in a clustered environment.

The issue is that the upgrade does not proceed in case both the machines in the cluster are running.

The error shown is

Product Name : Microsoft SQL Server
Product Version : 9.00.1399.06
Message Source : setup.rll
Message ID : 50000
EvtType : datastore\clustergroupsproperties.cpp@.InvokeSqlSetupDllAction@.ClusterGroupScope.SharedDisks@.0x2

It proceeds (with some errors) only if i stop the cluster service on the other machine. It is an expected behavior?

Does anyone have the documentation for this type of upgrade? Or just the basic steps to be followed.

http://www.sqlservercentral.com/columnists/ssamuel/2987.asp

http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

http://www.microsoft.com/downloads/details.aspx?FamilyID=3d5e96d9-0074-46c4-bd4f-c3eb2abf4b66&DisplayLang=en

check these links might be helpful

|||

In virtually every case of a cluster upgrade, I always tell my clients to perform a new install and not perform an in-place upgrade. If you have this option, take it. Upgrading in place is possible, but fraught with difficulties.

|||

I would need more information on your configuration and the exact steps you are going through. I wrote the section in the upgrade documentation for upgrading a cluster. I've upgraded both single instance and multi-instance clusters, in place, without any of the issues you are mentioning.

docs for 2003 enterprise cluster

Im looking for documentation that explains how to install SQL 2000
Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
running an install of Sage MMS 3.5 for SQL 2000 Server.
http://www.sage-eshop.com
Installing SQL2000 in a failover cluster is documented pretty well in SQL2000
Books Online under "Advanced Installation Options" and "Failover Clustering"
The content is not specific to Win2K3 or SAN. But as far as installing
SQL2000 itself is concerned whether it's Win2000 or Win2K3 or a shared disk
that is not presented from a SAN shouldn't matter. Configuring the cluster
itself at the OS level is different though. If you need to configure msdtc
yourself, read this KB article http://support.microsoft.com/?kbid=301600.
Linchi
"Scott" wrote:

> Im looking for documentation that explains how to install SQL 2000
> Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
> running an install of Sage MMS 3.5 for SQL 2000 Server.
> http://www.sage-eshop.com
>
>

docs for 2003 enterprise cluster

Im looking for documentation that explains how to install SQL 2000
Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
running an install of Sage MMS 3.5 for SQL 2000 Server.
---
http://www.sage-eshop.comInstalling SQL2000 in a failover cluster is documented pretty well in SQL200
0
Books Online under "Advanced Installation Options" and "Failover Clustering"
The content is not specific to Win2K3 or SAN. But as far as installing
SQL2000 itself is concerned whether it's Win2000 or Win2K3 or a shared disk
that is not presented from a SAN shouldn't matter. Configuring the cluster
itself at the OS level is different though. If you need to configure msdtc
yourself, read this KB article http://support.microsoft.com/?kbid=301600.
Linchi
"Scott" wrote:

> Im looking for documentation that explains how to install SQL 2000
> Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
> running an install of Sage MMS 3.5 for SQL 2000 Server.
> ---
> http://www.sage-eshop.com
>
>

docs for 2003 enterprise cluster

Im looking for documentation that explains how to install SQL 2000
Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
running an install of Sage MMS 3.5 for SQL 2000 Server.
---
http://www.sage-eshop.comInstalling SQL2000 in a failover cluster is documented pretty well in SQL2000
Books Online under "Advanced Installation Options" and "Failover Clustering"
The content is not specific to Win2K3 or SAN. But as far as installing
SQL2000 itself is concerned whether it's Win2000 or Win2K3 or a shared disk
that is not presented from a SAN shouldn't matter. Configuring the cluster
itself at the OS level is different though. If you need to configure msdtc
yourself, read this KB article http://support.microsoft.com/?kbid=301600.
Linchi
"Scott" wrote:
> Im looking for documentation that explains how to install SQL 2000
> Enterprise on Windows 2003 Enterprise (2 node-cluster) against a SAN? Im
> running an install of Sage MMS 3.5 for SQL 2000 Server.
> ---
> http://www.sage-eshop.com
>
>