new to sql and need some help. connectivity problems.

hi guy
i've installed sql on a dedicated box for the purpose of using it for mom and sms but the only problem is when i go to install sms or mom on the other boxes it doesnt see the sql server. however if i start the mom setup process on the sql box it sees the sql sever
i have installed the client tools on both the sms and mom boxes and configured them point to the sql server over tcp/ip and the named pipe but to no avail. i also added a data source to the odbc console thinking that may help but no it didnt
what i've done so fa
installed sql with integrated windows authenticatio
added it to a
got the Microsoft SQL Server 2000 Books Online from the ms sit
gone and purchased the ms sql server 2000 administration guid
started to read both books and am now scared of sql server 200
are there some connectivity tools that would help in troubleshooting this or am i barking up the wrong tree
i have used sms and mom extensively before but this is my first attempt at sql
cheer
dDid you install SQL Server or MSDE? Basically, on the client, you use SQL Server's "Client Network Utility"
and on the server, you use "Server Network Utility" to configure the connectivity. If you have MSDE, it
doesn't have network access turned on by default, and you won't have an icon for SNU, but it is there and the
name of the exe file is: svrnetcn.exe.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:1AFB725A-1AF3-47BC-808B-198916327FCA@.microsoft.com...
> hi guys
> i've installed sql on a dedicated box for the purpose of using it for mom and sms but the only problem is
when i go to install sms or mom on the other boxes it doesnt see the sql server. however if i start the mom
setup process on the sql box it sees the sql sever.
> i have installed the client tools on both the sms and mom boxes and configured them point to the sql server
over tcp/ip and the named pipe but to no avail. i also added a data source to the odbc console thinking that
may help but no it didnt.
> what i've done so far
> installed sql with integrated windows authentication
> added it to ad
> got the Microsoft SQL Server 2000 Books Online from the ms site
> gone and purchased the ms sql server 2000 administration guide
> started to read both books and am now scared of sql server 2000
> are there some connectivity tools that would help in troubleshooting this or am i barking up the wrong tree?
> i have used sms and mom extensively before but this is my first attempt at sql.
> cheers
> d

new to sql and need some help. connectivity problems.

hi guys
i've installed sql on a dedicated box for the purpose of using it for mom and sms but the only problem is when i go to install sms or mom on the other boxes it doesnt see the sql server. however if i start the mom setup process on the sql box it sees the
sql sever.
i have installed the client tools on both the sms and mom boxes and configured them point to the sql server over tcp/ip and the named pipe but to no avail. i also added a data source to the odbc console thinking that may help but no it didnt.
what i've done so far
installed sql with integrated windows authentication
added it to ad
got the Microsoft SQL Server 2000 Books Online from the ms site
gone and purchased the ms sql server 2000 administration guide
started to read both books and am now scared of sql server 2000
are there some connectivity tools that would help in troubleshooting this or am i barking up the wrong tree?
i have used sms and mom extensively before but this is my first attempt at sql.
cheers
d
Did you install SQL Server or MSDE? Basically, on the client, you use SQL Server's "Client Network Utility"
and on the server, you use "Server Network Utility" to configure the connectivity. If you have MSDE, it
doesn't have network access turned on by default, and you won't have an icon for SNU, but it is there and the
name of the exe file is: svrnetcn.exe.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:1AFB725A-1AF3-47BC-808B-198916327FCA@.microsoft.com...
> hi guys
> i've installed sql on a dedicated box for the purpose of using it for mom and sms but the only problem is
when i go to install sms or mom on the other boxes it doesnt see the sql server. however if i start the mom
setup process on the sql box it sees the sql sever.
> i have installed the client tools on both the sms and mom boxes and configured them point to the sql server
over tcp/ip and the named pipe but to no avail. i also added a data source to the odbc console thinking that
may help but no it didnt.
> what i've done so far
> installed sql with integrated windows authentication
> added it to ad
> got the Microsoft SQL Server 2000 Books Online from the ms site
> gone and purchased the ms sql server 2000 administration guide
> started to read both books and am now scared of sql server 2000
> are there some connectivity tools that would help in troubleshooting this or am i barking up the wrong tree?
> i have used sms and mom extensively before but this is my first attempt at sql.
> cheers
> d

new to sql and need some help. connectivity problems.

hi guys
i've installed sql on a dedicated box for the purpose of using it for mom an
d sms but the only problem is when i go to install sms or mom on the other b
oxes it doesnt see the sql server. however if i start the mom setup process
on the sql box it sees the
sql sever.
i have installed the client tools on both the sms and mom boxes and configur
ed them point to the sql server over tcp/ip and the named pipe but to no ava
il. i also added a data source to the odbc console thinking that may help bu
t no it didnt.
what i've done so far
installed sql with integrated windows authentication
added it to ad
got the Microsoft SQL Server 2000 Books Online from the ms site
gone and purchased the ms sql server 2000 administration guide
started to read both books and am now scared of sql server 2000
are there some connectivity tools that would help in troubleshooting this or
am i barking up the wrong tree?
i have used sms and mom extensively before but this is my first attempt at s
ql.
cheers
dDid you install SQL Server or MSDE? Basically, on the client, you use SQL Se
rver's "Client Network Utility"
and on the server, you use "Server Network Utility" to configure the connect
ivity. If you have MSDE, it
doesn't have network access turned on by default, and you won't have an icon
for SNU, but it is there and the
name of the exe file is: svrnetcn.exe.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:1AFB725A-1AF3-47BC-808B-198916327FCA@.microsoft.com...
> hi guys
> i've installed sql on a dedicated box for the purpose of using it for mom and sms
but the only problem is
when i go to install sms or mom on the other boxes it doesnt see the sql ser
ver. however if i start the mom
setup process on the sql box it sees the sql sever.
> i have installed the client tools on both the sms and mom boxes and configured the
m point to the sql server
over tcp/ip and the named pipe but to no avail. i also added a data source t
o the odbc console thinking that
may help but no it didnt.
> what i've done so far
> installed sql with integrated windows authentication
> added it to ad
> got the Microsoft SQL Server 2000 Books Online from the ms site
> gone and purchased the ms sql server 2000 administration guide
> started to read both books and am now scared of sql server 2000
> are there some connectivity tools that would help in troubleshooting this
or am i barking up the wrong tree?
> i have used sms and mom extensively before but this is my first attempt at
sql.
> cheers
> d

New to MSDE (but not SQL)

All,
looking to distribute MSDE with my ASP.NET app... looking for two pieces:
1) Is there a way to install MSDE with a DB already attached? I want to
install MSDE and then attach a DB, but attaching has to come after a
reboot(to start after services restart), and I would rather do it all at the
same time...
2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my app
for the client
MTIA
wardeaux
> 2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my
app
> for the client
http://www.aspfaq.com/2442
http://www.aspfaq.com/
(Reverse address to reply.)
|||1) Nope. You don't have to reboot the computer when you install MSDE though,
strictly speaking.
2) SQL Server Web Data Administrator:
http://www.microsoft.com/downloads/d...displaylang=en
Jacco Schalkwijk
SQL Server MVP
"Wardeaux" <wardeaux@.bellsouth.net> wrote in message
news:e10zJ72jEHA.3196@.TK2MSFTNGP10.phx.gbl...
> All,
> looking to distribute MSDE with my ASP.NET app... looking for two pieces:
> 1) Is there a way to install MSDE with a DB already attached? I want to
> install MSDE and then attach a DB, but attaching has to come after a
> reboot(to start after services restart), and I would rather do it all at
> the
> same time...
> 2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my
> app
> for the client
> MTIA
> wardeaux
>
|||You don't necessarily need to reboot after installing. To start MSDE after
installing, just run "net start mssql$instancename" (if installing as a
named instance) or use scm.exe. You may want to start SQL Server Agent
also.
Distribute your database's .mdf and .ldf files and attach them using
osql.exe to execute the sp_attach_db stored procedure.
"Wardeaux" <wardeaux@.bellsouth.net> wrote in message
news:e10zJ72jEHA.3196@.TK2MSFTNGP10.phx.gbl...
> All,
> looking to distribute MSDE with my ASP.NET app... looking for two
pieces:
> 1) Is there a way to install MSDE with a DB already attached? I want to
> install MSDE and then attach a DB, but attaching has to come after a
> reboot(to start after services restart), and I would rather do it all at
the
> same time...
> 2) Good Freeware/Almost-freeware MSDE manager I can redistribute with my
app
> for the client
> MTIA
> wardeaux
>
sql

new SSRS install, works great until I try to access Oracle datasource - System.Data.Oracle

re: new SSRS install, works great until I try to access Oracle
datasource - System.Data.OracleClient requires Oracle client software
>From my desktop the report accessing an Oracle 9i db with no problem.
I've deployed other reports accesing sql server with no problem.
Now I deploy the report and try to access my Oracle source and get:
System.Data.OracleClient requires Oracle client software version 8.1.7
or greater
On the server in question, I know they've installed the oracle client.
I can access the db from sql plus with no problem.
As the user that I access ssrs credentials, i remote login and am able
to write to oracle home.. C:\oracle\ora10g\NETWORK\ADMIN
i've confirmed my database is in tnsnames and it works from sqlplus.On Nov 5, 3:27 pm, jobs <j...@.webdos.com> wrote:
> re: new SSRS install, works great until I try to access Oracle
> datasource - System.Data.OracleClient requires Oracle client software
> >From my desktop the report accessing an Oracle 9i db with no problem.
> I've deployed other reports accesing sql server with no problem.
> Now I deploy the report and try to access my Oracle source and get:
> System.Data.OracleClient requires Oracle client software version 8.1.7
> or greater
> On the server in question, I know they've installed the oracle client.
> I can access the db from sql plus with no problem.
> As the user that I access ssrs credentials, i remote login and am abl
> to write to oracle home.. C:\oracle\ora10g\NETWORK\ADMIN
> i've confirmed my database is in tnsnames and it works from sqlplus.
This is just a guess; but, have you checked for all necessary assembly
references from the Oracle-side. I would start with maybe getting a
comparison tool (possibly 30-day trial version of Merge 2007:
http://www.araxis.com/ ) and compare the directory structure of your
machine versus the machine where the report is deployed (in reference
to Oracle 8.1.7). Also, you might want to check into the driver for
the SSRS connection to Oracle. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||If you have the Oracle client installed on the server I think the issue is
that the directory it is installed in is not accessible to RS. I googled
this a little (oracle client reporting services permissions)
http://technet.microsoft.com/en-us/library/ms159689.aspx
a.. (Optional) Install Oracle client tools on the report server if your
reports use the Microsoft .NET Framework Data Provider for Oracle. After you
install the client tools, you must restart IIS. To support subscriptions to
reports that use Oracle data sources, you must grant permissions to the
NetworkService account. For more information, see
http://support.microsoft.com/kb/870668.
http://support.microsoft.com/kb/870668
To work around this problem, add permissions for the NETWORK SERVICE
security principal to the Oracle\Oracle version\bin directory and to the
Oracle\Oracle version\network\admin directory. To do this, follow these
steps. ...
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jobs" <jobs@.webdos.com> wrote in message
news:1194298047.081192.142180@.o3g2000hsb.googlegroups.com...
> re: new SSRS install, works great until I try to access Oracle
> datasource - System.Data.OracleClient requires Oracle client software
>
>>From my desktop the report accessing an Oracle 9i db with no problem.
> I've deployed other reports accesing sql server with no problem.
> Now I deploy the report and try to access my Oracle source and get:
> System.Data.OracleClient requires Oracle client software version 8.1.7
> or greater
> On the server in question, I know they've installed the oracle client.
> I can access the db from sql plus with no problem.
> As the user that I access ssrs credentials, i remote login and am able
> to write to oracle home.. C:\oracle\ora10g\NETWORK\ADMIN
> i've confirmed my database is in tnsnames and it works from sqlplus.
>

New SQL Server Install Advice

I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
containers as the machine has a PERC 4 controller. The machine has x2 73GB
SCSI and x4 146GB SCSI HDD.
Container 1
--
The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which has
56GB free.
Container 2
--
A D drive for Data I created and also L for Log which I assigned as dynamic
drives.
Is this setup Ok for running SQL2000. The Data files will reside in D and
the Log files will reside in L. Is this Ok for the read/write access that
occurs when SQL is accessed?
Please help.
skcI assume there is at least one processor and some memory on the server as
well.
It will work. It depends on what performance, capacity, and availability
you are needing.
"Skc" <Skc@.discussions.microsoft.com> wrote in message
news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> containers as the machine has a PERC 4 controller. The machine has x2
> 73GB
> SCSI and x4 146GB SCSI HDD.
> Container 1
> --
> The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> has
> 56GB free.
> Container 2
> --
> A D drive for Data I created and also L for Log which I assigned as
> dynamic
> drives.
> Is this setup Ok for running SQL2000. The Data files will reside in D and
> the Log files will reside in L. Is this Ok for the read/write access that
> occurs when SQL is accessed?
> Please help.
> skc|||Xeon 2.8 x2 and 2GB RAM.
We want max. performance. Is this OK?
Furthermore, I installed SQL2000 and it came with 4 CDs:
1> SQL 2000 Standard (Personal)
2> SQL 2000 Standard
3> SP4
4> Reporting Tools
I installed Disk #1, asked me no product key, I selected 5 CALS from the
dropdown (which was how many I bought) and that was it. I have the SQL
Service running and the SQL Tools (enterprise manager). What is the
difference between the 2 Cds mentioned above?
In Enterprise Manager, when I right-click the (local) Server, it says I have
Microsoft SQL Server Std Edition installed. This is very odd, I hope I have
done this right as it did not ask for a serial product key or anything.
Please verify the above it OK.
"Danny" wrote:

> I assume there is at least one processor and some memory on the server as
> well.
> It will work. It depends on what performance, capacity, and availability
> you are needing.
> "Skc" <Skc@.discussions.microsoft.com> wrote in message
> news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>
>

New SQL Server Install Advice

I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
containers as the machine has a PERC 4 controller. The machine has x2 73GB
SCSI and x4 146GB SCSI HDD.
Container 1
The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which has
56GB free.
Container 2
A D drive for Data I created and also L for Log which I assigned as dynamic
drives.
Is this setup Ok for running SQL2000. The Data files will reside in D and
the Log files will reside in L. Is this Ok for the read/write access that
occurs when SQL is accessed?
Please help.
skc
I assume there is at least one processor and some memory on the server as
well.
It will work. It depends on what performance, capacity, and availability
you are needing.
"Skc" <Skc@.discussions.microsoft.com> wrote in message
news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> containers as the machine has a PERC 4 controller. The machine has x2
> 73GB
> SCSI and x4 146GB SCSI HDD.
> Container 1
> --
> The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> has
> 56GB free.
> Container 2
> --
> A D drive for Data I created and also L for Log which I assigned as
> dynamic
> drives.
> Is this setup Ok for running SQL2000. The Data files will reside in D and
> the Log files will reside in L. Is this Ok for the read/write access that
> occurs when SQL is accessed?
> Please help.
> skc
|||Xeon 2.8 x2 and 2GB RAM.
We want max. performance. Is this OK?
Furthermore, I installed SQL2000 and it came with 4 CDs:
1> SQL 2000 Standard (Personal)
2> SQL 2000 Standard
3> SP4
4> Reporting Tools
I installed Disk #1, asked me no product key, I selected 5 CALS from the
dropdown (which was how many I bought) and that was it. I have the SQL
Service running and the SQL Tools (enterprise manager). What is the
difference between the 2 Cds mentioned above?
In Enterprise Manager, when I right-click the (local) Server, it says I have
Microsoft SQL Server Std Edition installed. This is very odd, I hope I have
done this right as it did not ask for a serial product key or anything.
Please verify the above it OK.
"Danny" wrote:

> I assume there is at least one processor and some memory on the server as
> well.
> It will work. It depends on what performance, capacity, and availability
> you are needing.
> "Skc" <Skc@.discussions.microsoft.com> wrote in message
> news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>
>

New SQL Server Install Advice

I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
containers as the machine has a PERC 4 controller. The machine has x2 73GB
SCSI and x4 146GB SCSI HDD.
Container 1
--
The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which has
56GB free.
Container 2
--
A D drive for Data I created and also L for Log which I assigned as dynamic
drives.
Is this setup Ok for running SQL2000. The Data files will reside in D and
the Log files will reside in L. Is this Ok for the read/write access that
occurs when SQL is accessed?
Please help.
skcI assume there is at least one processor and some memory on the server as
well.
It will work. It depends on what performance, capacity, and availability
you are needing.
"Skc" <Skc@.discussions.microsoft.com> wrote in message
news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
>I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> containers as the machine has a PERC 4 controller. The machine has x2
> 73GB
> SCSI and x4 146GB SCSI HDD.
> Container 1
> --
> The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> has
> 56GB free.
> Container 2
> --
> A D drive for Data I created and also L for Log which I assigned as
> dynamic
> drives.
> Is this setup Ok for running SQL2000. The Data files will reside in D and
> the Log files will reside in L. Is this Ok for the read/write access that
> occurs when SQL is accessed?
> Please help.
> skc|||Xeon 2.8 x2 and 2GB RAM.
We want max. performance. Is this OK?
Furthermore, I installed SQL2000 and it came with 4 CDs:
1> SQL 2000 Standard (Personal)
2> SQL 2000 Standard
3> SP4
4> Reporting Tools
I installed Disk #1, asked me no product key, I selected 5 CALS from the
dropdown (which was how many I bought) and that was it. I have the SQL
Service running and the SQL Tools (enterprise manager). What is the
difference between the 2 Cds mentioned above?
In Enterprise Manager, when I right-click the (local) Server, it says I have
Microsoft SQL Server Std Edition installed. This is very odd, I hope I have
done this right as it did not ask for a serial product key or anything.
Please verify the above it OK.
"Danny" wrote:
> I assume there is at least one processor and some memory on the server as
> well.
> It will work. It depends on what performance, capacity, and availability
> you are needing.
> "Skc" <Skc@.discussions.microsoft.com> wrote in message
> news:46CDFADB-7AC6-4719-B0A8-8154D6977397@.microsoft.com...
> >I have a new Dell PowerEdge 2800 running windows 2003. I have 2 RAID
> > containers as the machine has a PERC 4 controller. The machine has x2
> > 73GB
> > SCSI and x4 146GB SCSI HDD.
> >
> > Container 1
> > --
> > The OS C drive (partition of 12GB) is in RAID 1 and so is E drive which
> > has
> > 56GB free.
> >
> > Container 2
> > --
> > A D drive for Data I created and also L for Log which I assigned as
> > dynamic
> > drives.
> >
> > Is this setup Ok for running SQL2000. The Data files will reside in D and
> > the Log files will reside in L. Is this Ok for the read/write access that
> > occurs when SQL is accessed?
> >
> > Please help.
> >
> > skc
>
>

New SQL Server Install

We just went through a catastrophic failure of an Oracle database. This
database was running on a server with a RAID 5 installed. One of the disks
was having read/write errors. When we pulled the disk from the array to
have the hot spare kick in, the Oracle server failed and it took a lot of
effort to get it back. (I hate oracle).
We are moving to SQL Server 2005 and want to avoid this problem. I have
been asked to get the specs for a cluster. I have been reading up on the
clustering, but came across Transaction Log Shipping. I know that the
Transaction Log shipping does not have an automatic fail over, but it will
move the transaction log to another server and provide another server we can
use for reporting and in the event of a failure on the main server, we could
use the other server until we can bring it up on line.
What in your opinion would be a better solution, cluster or transaction log
shipping? All of our programs will be using this data, and it is important
to recover from a disaster like this as quickly as possible. The cost of
clustering may be preventative, so I would like your input for those who
have used one or both methods for pros and cons. Thanks.
JohnSince you are using SQL Server 2005, consider database mirroring. You don't
need the fancy hardware that clustering does and failover is very quick -
and can be automatic. Also, you can do a database snapshot on the mirror
and use it for reporting.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"John Wright" <riley_wrightx@.hotmail.com> wrote in message
news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
We just went through a catastrophic failure of an Oracle database. This
database was running on a server with a RAID 5 installed. One of the disks
was having read/write errors. When we pulled the disk from the array to
have the hot spare kick in, the Oracle server failed and it took a lot of
effort to get it back. (I hate oracle).
We are moving to SQL Server 2005 and want to avoid this problem. I have
been asked to get the specs for a cluster. I have been reading up on the
clustering, but came across Transaction Log Shipping. I know that the
Transaction Log shipping does not have an automatic fail over, but it will
move the transaction log to another server and provide another server we can
use for reporting and in the event of a failure on the main server, we could
use the other server until we can bring it up on line.
What in your opinion would be a better solution, cluster or transaction log
shipping? All of our programs will be using this data, and it is important
to recover from a disaster like this as quickly as possible. The cost of
clustering may be preventative, so I would like your input for those who
have used one or both methods for pros and cons. Thanks.
John|||Isn't SQL Server Enterprise edition the only edition that allows for
snapshots? We plan on using Standard Edition which will support two
clusters.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Since you are using SQL Server 2005, consider database mirroring. You
> don't
> need the fancy hardware that clustering does and failover is very quick -
> and can be automatic. Also, you can do a database snapshot on the mirror
> and use it for reporting.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
> We just went through a catastrophic failure of an Oracle database. This
> database was running on a server with a RAID 5 installed. One of the disks
> was having read/write errors. When we pulled the disk from the array to
> have the hot spare kick in, the Oracle server failed and it took a lot of
> effort to get it back. (I hate oracle).
> We are moving to SQL Server 2005 and want to avoid this problem. I have
> been asked to get the specs for a cluster. I have been reading up on the
> clustering, but came across Transaction Log Shipping. I know that the
> Transaction Log shipping does not have an automatic fail over, but it will
> move the transaction log to another server and provide another server we
> can
> use for reporting and in the event of a failure on the main server, we
> could
> use the other server until we can bring it up on line.
> What in your opinion would be a better solution, cluster or transaction
> log
> shipping? All of our programs will be using this data, and it is
> important
> to recover from a disaster like this as quickly as possible. The cost of
> clustering may be preventative, so I would like your input for those who
> have used one or both methods for pros and cons. Thanks.
> John
>
>|||Yes, EE is required for database snapshots. Mirroring is available for SE but only on sync mode and
only one REDO thread.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"John Wright" <riley_wrightx@.hotmail.com> wrote in message
news:%23In0b5eXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Isn't SQL Server Enterprise edition the only edition that allows for snapshots? We plan on using
> Standard Edition which will support two clusters.
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Since you are using SQL Server 2005, consider database mirroring. You don't
>> need the fancy hardware that clustering does and failover is very quick -
>> and can be automatic. Also, you can do a database snapshot on the mirror
>> and use it for reporting.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
>> We just went through a catastrophic failure of an Oracle database. This
>> database was running on a server with a RAID 5 installed. One of the disks
>> was having read/write errors. When we pulled the disk from the array to
>> have the hot spare kick in, the Oracle server failed and it took a lot of
>> effort to get it back. (I hate oracle).
>> We are moving to SQL Server 2005 and want to avoid this problem. I have
>> been asked to get the specs for a cluster. I have been reading up on the
>> clustering, but came across Transaction Log Shipping. I know that the
>> Transaction Log shipping does not have an automatic fail over, but it will
>> move the transaction log to another server and provide another server we can
>> use for reporting and in the event of a failure on the main server, we could
>> use the other server until we can bring it up on line.
>> What in your opinion would be a better solution, cluster or transaction log
>> shipping? All of our programs will be using this data, and it is important
>> to recover from a disaster like this as quickly as possible. The cost of
>> clustering may be preventative, so I would like your input for those who
>> have used one or both methods for pros and cons. Thanks.
>> John
>>
>|||Yes, snapshots are supported only in Ent Ed. Also, Std Edition supports
2-node clusters - not "two clusters". It depends on where you want to put
your money and what your needs are. When it comes to High Availability
(HA), then you often have to go to Ent Ed. If you want clustering and have
only 2 nodes, then you can get away with Std Ed, but clustering hardware is
usually a bit more expensive and a little trickier to set up. Mirroring
will work on regular hardware and can go between dissimilar platforms.
Automatic failover, though is available in the Ent Ed.
When it comes to reporting, snapshots are your friend. Log shipping is fine
for HA, but you can't report off of the destination DB.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"John Wright" <riley_wrightx@.hotmail.com> wrote in message
news:%23In0b5eXIHA.4440@.TK2MSFTNGP06.phx.gbl...
Isn't SQL Server Enterprise edition the only edition that allows for
snapshots? We plan on using Standard Edition which will support two
clusters.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Since you are using SQL Server 2005, consider database mirroring. You
> don't
> need the fancy hardware that clustering does and failover is very quick -
> and can be automatic. Also, you can do a database snapshot on the mirror
> and use it for reporting.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
> We just went through a catastrophic failure of an Oracle database. This
> database was running on a server with a RAID 5 installed. One of the disks
> was having read/write errors. When we pulled the disk from the array to
> have the hot spare kick in, the Oracle server failed and it took a lot of
> effort to get it back. (I hate oracle).
> We are moving to SQL Server 2005 and want to avoid this problem. I have
> been asked to get the specs for a cluster. I have been reading up on the
> clustering, but came across Transaction Log Shipping. I know that the
> Transaction Log shipping does not have an automatic fail over, but it will
> move the transaction log to another server and provide another server we
> can
> use for reporting and in the event of a failure on the main server, we
> could
> use the other server until we can bring it up on line.
> What in your opinion would be a better solution, cluster or transaction
> log
> shipping? All of our programs will be using this data, and it is
> important
> to recover from a disaster like this as quickly as possible. The cost of
> clustering may be preventative, so I would like your input for those who
> have used one or both methods for pros and cons. Thanks.
> John
>
>|||> Log shipping is fine
> for HA, but you can't report off of the destination DB.
Well, you can if you do the restores using STANDBY. But you'd have to kick out the users each time
you want to do the next restore. Which means that you really ... can't use a log shipped database
for reporting ;-).
(Just wanted to mention this before anyone else say "You can". )
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uy0aAMfXIHA.1188@.TK2MSFTNGP04.phx.gbl...
> Yes, snapshots are supported only in Ent Ed. Also, Std Edition supports
> 2-node clusters - not "two clusters". It depends on where you want to put
> your money and what your needs are. When it comes to High Availability
> (HA), then you often have to go to Ent Ed. If you want clustering and have
> only 2 nodes, then you can get away with Std Ed, but clustering hardware is
> usually a bit more expensive and a little trickier to set up. Mirroring
> will work on regular hardware and can go between dissimilar platforms.
> Automatic failover, though is available in the Ent Ed.
> When it comes to reporting, snapshots are your friend. Log shipping is fine
> for HA, but you can't report off of the destination DB.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
> news:%23In0b5eXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Isn't SQL Server Enterprise edition the only edition that allows for
> snapshots? We plan on using Standard Edition which will support two
> clusters.
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Since you are using SQL Server 2005, consider database mirroring. You
>> don't
>> need the fancy hardware that clustering does and failover is very quick -
>> and can be automatic. Also, you can do a database snapshot on the mirror
>> and use it for reporting.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
>> We just went through a catastrophic failure of an Oracle database. This
>> database was running on a server with a RAID 5 installed. One of the disks
>> was having read/write errors. When we pulled the disk from the array to
>> have the hot spare kick in, the Oracle server failed and it took a lot of
>> effort to get it back. (I hate oracle).
>> We are moving to SQL Server 2005 and want to avoid this problem. I have
>> been asked to get the specs for a cluster. I have been reading up on the
>> clustering, but came across Transaction Log Shipping. I know that the
>> Transaction Log shipping does not have an automatic fail over, but it will
>> move the transaction log to another server and provide another server we
>> can
>> use for reporting and in the event of a failure on the main server, we
>> could
>> use the other server until we can bring it up on line.
>> What in your opinion would be a better solution, cluster or transaction
>> log
>> shipping? All of our programs will be using this data, and it is
>> important
>> to recover from a disaster like this as quickly as possible. The cost of
>> clustering may be preventative, so I would like your input for those who
>> have used one or both methods for pros and cons. Thanks.
>> John
>>
>
>|||Low-end clusters have definitely gotten cheaper over the past few years.
Look at some of the dual-socket HP stuff and you can put together a good,
stable, basic cluster for under six figures.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uy0aAMfXIHA.1188@.TK2MSFTNGP04.phx.gbl...
> Yes, snapshots are supported only in Ent Ed. Also, Std Edition supports
> 2-node clusters - not "two clusters". It depends on where you want to put
> your money and what your needs are. When it comes to High Availability
> (HA), then you often have to go to Ent Ed. If you want clustering and
> have
> only 2 nodes, then you can get away with Std Ed, but clustering hardware
> is
> usually a bit more expensive and a little trickier to set up. Mirroring
> will work on regular hardware and can go between dissimilar platforms.
> Automatic failover, though is available in the Ent Ed.
> When it comes to reporting, snapshots are your friend. Log shipping is
> fine
> for HA, but you can't report off of the destination DB.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
> news:%23In0b5eXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Isn't SQL Server Enterprise edition the only edition that allows for
> snapshots? We plan on using Standard Edition which will support two
> clusters.
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Since you are using SQL Server 2005, consider database mirroring. You
>> don't
>> need the fancy hardware that clustering does and failover is very quick -
>> and can be automatic. Also, you can do a database snapshot on the mirror
>> and use it for reporting.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
>> We just went through a catastrophic failure of an Oracle database. This
>> database was running on a server with a RAID 5 installed. One of the
>> disks
>> was having read/write errors. When we pulled the disk from the array to
>> have the hot spare kick in, the Oracle server failed and it took a lot of
>> effort to get it back. (I hate oracle).
>> We are moving to SQL Server 2005 and want to avoid this problem. I have
>> been asked to get the specs for a cluster. I have been reading up on the
>> clustering, but came across Transaction Log Shipping. I know that the
>> Transaction Log shipping does not have an automatic fail over, but it
>> will
>> move the transaction log to another server and provide another server we
>> can
>> use for reporting and in the event of a failure on the main server, we
>> could
>> use the other server until we can bring it up on line.
>> What in your opinion would be a better solution, cluster or transaction
>> log
>> shipping? All of our programs will be using this data, and it is
>> important
>> to recover from a disaster like this as quickly as possible. The cost of
>> clustering may be preventative, so I would like your input for those who
>> have used one or both methods for pros and cons. Thanks.
>> John
>>
>
>|||Waaaaaay back in 2000, we created our own jobs to logship and only had the
restore command run every 8 hours. All the files were there, and we could
catch the whole thing up in about 20 minutes if the primary went down, but
it was a reporting server all day :)
Same thing could be done here if Log Shipping was desired, as well as
reporting. May not be the most glamorous solution, but it works...
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:0875841B-779E-4639-9C7F-31D19FCF060A@.microsoft.com...
>> Log shipping is fine
>> for HA, but you can't report off of the destination DB.
> Well, you can if you do the restores using STANDBY. But you'd have to kick
> out the users each time you want to do the next restore. Which means that
> you really ... can't use a log shipped database for reporting ;-).
> (Just wanted to mention this before anyone else say "You can". )
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:uy0aAMfXIHA.1188@.TK2MSFTNGP04.phx.gbl...
>> Yes, snapshots are supported only in Ent Ed. Also, Std Edition supports
>> 2-node clusters - not "two clusters". It depends on where you want to
>> put
>> your money and what your needs are. When it comes to High Availability
>> (HA), then you often have to go to Ent Ed. If you want clustering and
>> have
>> only 2 nodes, then you can get away with Std Ed, but clustering hardware
>> is
>> usually a bit more expensive and a little trickier to set up. Mirroring
>> will work on regular hardware and can go between dissimilar platforms.
>> Automatic failover, though is available in the Ent Ed.
>> When it comes to reporting, snapshots are your friend. Log shipping is
>> fine
>> for HA, but you can't report off of the destination DB.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:%23In0b5eXIHA.4440@.TK2MSFTNGP06.phx.gbl...
>> Isn't SQL Server Enterprise edition the only edition that allows for
>> snapshots? We plan on using Standard Edition which will support two
>> clusters.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Since you are using SQL Server 2005, consider database mirroring. You
>> don't
>> need the fancy hardware that clustering does and failover is very
>> quick -
>> and can be automatic. Also, you can do a database snapshot on the
>> mirror
>> and use it for reporting.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
>> We just went through a catastrophic failure of an Oracle database. This
>> database was running on a server with a RAID 5 installed. One of the
>> disks
>> was having read/write errors. When we pulled the disk from the array to
>> have the hot spare kick in, the Oracle server failed and it took a lot
>> of
>> effort to get it back. (I hate oracle).
>> We are moving to SQL Server 2005 and want to avoid this problem. I have
>> been asked to get the specs for a cluster. I have been reading up on
>> the
>> clustering, but came across Transaction Log Shipping. I know that the
>> Transaction Log shipping does not have an automatic fail over, but it
>> will
>> move the transaction log to another server and provide another server we
>> can
>> use for reporting and in the event of a failure on the main server, we
>> could
>> use the other server until we can bring it up on line.
>> What in your opinion would be a better solution, cluster or transaction
>> log
>> shipping? All of our programs will be using this data, and it is
>> important
>> to recover from a disaster like this as quickly as possible. The cost
>> of
>> clustering may be preventative, so I would like your input for those who
>> have used one or both methods for pros and cons. Thanks.
>> John
>>
>>
>>
>|||Yeah, I figured I'd give him the "short answer". Of course, if you want,
you can have the log shipping sync on a daily schedule and use STANDBY.
That could be a poor man's way of doing mirroring with a daily snapshot.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:0875841B-779E-4639-9C7F-31D19FCF060A@.microsoft.com...
> Log shipping is fine
> for HA, but you can't report off of the destination DB.
Well, you can if you do the restores using STANDBY. But you'd have to kick
out the users each time
you want to do the next restore. Which means that you really ... can't use a
log shipped database
for reporting ;-).
(Just wanted to mention this before anyone else say "You can". )
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:uy0aAMfXIHA.1188@.TK2MSFTNGP04.phx.gbl...
> Yes, snapshots are supported only in Ent Ed. Also, Std Edition supports
> 2-node clusters - not "two clusters". It depends on where you want to put
> your money and what your needs are. When it comes to High Availability
> (HA), then you often have to go to Ent Ed. If you want clustering and
have
> only 2 nodes, then you can get away with Std Ed, but clustering hardware
is
> usually a bit more expensive and a little trickier to set up. Mirroring
> will work on regular hardware and can go between dissimilar platforms.
> Automatic failover, though is available in the Ent Ed.
> When it comes to reporting, snapshots are your friend. Log shipping is
fine
> for HA, but you can't report off of the destination DB.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
> news:%23In0b5eXIHA.4440@.TK2MSFTNGP06.phx.gbl...
> Isn't SQL Server Enterprise edition the only edition that allows for
> snapshots? We plan on using Standard Edition which will support two
> clusters.
>
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Since you are using SQL Server 2005, consider database mirroring. You
>> don't
>> need the fancy hardware that clustering does and failover is very quick -
>> and can be automatic. Also, you can do a database snapshot on the mirror
>> and use it for reporting.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
>> We just went through a catastrophic failure of an Oracle database. This
>> database was running on a server with a RAID 5 installed. One of the
disks
>> was having read/write errors. When we pulled the disk from the array to
>> have the hot spare kick in, the Oracle server failed and it took a lot of
>> effort to get it back. (I hate oracle).
>> We are moving to SQL Server 2005 and want to avoid this problem. I have
>> been asked to get the specs for a cluster. I have been reading up on the
>> clustering, but came across Transaction Log Shipping. I know that the
>> Transaction Log shipping does not have an automatic fail over, but it
will
>> move the transaction log to another server and provide another server we
>> can
>> use for reporting and in the event of a failure on the main server, we
>> could
>> use the other server until we can bring it up on line.
>> What in your opinion would be a better solution, cluster or transaction
>> log
>> shipping? All of our programs will be using this data, and it is
>> important
>> to recover from a disaster like this as quickly as possible. The cost of
>> clustering may be preventative, so I would like your input for those who
>> have used one or both methods for pros and cons. Thanks.
>> John
>>
>
>|||Way back 1.5 years ago I did the same thing for a client with thousands of
databases. Worked like a champ.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:%23v1x6WfXIHA.4696@.TK2MSFTNGP05.phx.gbl...
> Waaaaaay back in 2000, we created our own jobs to logship and only had the
> restore command run every 8 hours. All the files were there, and we could
> catch the whole thing up in about 20 minutes if the primary went down, but
> it was a reporting server all day :)
> Same thing could be done here if Log Shipping was desired, as well as
> reporting. May not be the most glamorous solution, but it works...
> --
> Kevin3NF
> SQL Server dude
> You want fries with that?
> http://kevin3nf.blogspot.com/
> I only check the newsgroups during work hours, M-F.
> Hit my blog and the contact links if necessary...I may be available.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:0875841B-779E-4639-9C7F-31D19FCF060A@.microsoft.com...
>> Log shipping is fine
>> for HA, but you can't report off of the destination DB.
>> Well, you can if you do the restores using STANDBY. But you'd have to
>> kick out the users each time you want to do the next restore. Which means
>> that you really ... can't use a log shipped database for reporting ;-).
>> (Just wanted to mention this before anyone else say "You can". )
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:uy0aAMfXIHA.1188@.TK2MSFTNGP04.phx.gbl...
>> Yes, snapshots are supported only in Ent Ed. Also, Std Edition supports
>> 2-node clusters - not "two clusters". It depends on where you want to
>> put
>> your money and what your needs are. When it comes to High Availability
>> (HA), then you often have to go to Ent Ed. If you want clustering and
>> have
>> only 2 nodes, then you can get away with Std Ed, but clustering hardware
>> is
>> usually a bit more expensive and a little trickier to set up. Mirroring
>> will work on regular hardware and can go between dissimilar platforms.
>> Automatic failover, though is available in the Ent Ed.
>> When it comes to reporting, snapshots are your friend. Log shipping is
>> fine
>> for HA, but you can't report off of the destination DB.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:%23In0b5eXIHA.4440@.TK2MSFTNGP06.phx.gbl...
>> Isn't SQL Server Enterprise edition the only edition that allows for
>> snapshots? We plan on using Standard Edition which will support two
>> clusters.
>>
>> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
>> news:ee6ZxueXIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Since you are using SQL Server 2005, consider database mirroring. You
>> don't
>> need the fancy hardware that clustering does and failover is very
>> quick -
>> and can be automatic. Also, you can do a database snapshot on the
>> mirror
>> and use it for reporting.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
>> SQL Server MVP
>> Toronto, ON Canada
>> https://mvp.support.microsoft.com/profile/Tom.Moreau
>>
>> "John Wright" <riley_wrightx@.hotmail.com> wrote in message
>> news:u6BTxreXIHA.3400@.TK2MSFTNGP03.phx.gbl...
>> We just went through a catastrophic failure of an Oracle database.
>> This
>> database was running on a server with a RAID 5 installed. One of the
>> disks
>> was having read/write errors. When we pulled the disk from the array
>> to
>> have the hot spare kick in, the Oracle server failed and it took a lot
>> of
>> effort to get it back. (I hate oracle).
>> We are moving to SQL Server 2005 and want to avoid this problem. I
>> have
>> been asked to get the specs for a cluster. I have been reading up on
>> the
>> clustering, but came across Transaction Log Shipping. I know that the
>> Transaction Log shipping does not have an automatic fail over, but it
>> will
>> move the transaction log to another server and provide another server
>> we
>> can
>> use for reporting and in the event of a failure on the main server, we
>> could
>> use the other server until we can bring it up on line.
>> What in your opinion would be a better solution, cluster or transaction
>> log
>> shipping? All of our programs will be using this data, and it is
>> important
>> to recover from a disaster like this as quickly as possible. The cost
>> of
>> clustering may be preventative, so I would like your input for those
>> who
>> have used one or both methods for pros and cons. Thanks.
>> John
>>
>>
>>
>|||Just a word of caution to help manage the expectation. If your storage goes
bad, you can for sure leverage certain DBMS features to alleviate the pain.
But there is no magic. SQL Server offers you many good features, but the same
potential storage problems won't magically go away. Due diligence is required
to plan for storage disasters.
Linchi
"John Wright" wrote:
> We just went through a catastrophic failure of an Oracle database. This
> database was running on a server with a RAID 5 installed. One of the disks
> was having read/write errors. When we pulled the disk from the array to
> have the hot spare kick in, the Oracle server failed and it took a lot of
> effort to get it back. (I hate oracle).
> We are moving to SQL Server 2005 and want to avoid this problem. I have
> been asked to get the specs for a cluster. I have been reading up on the
> clustering, but came across Transaction Log Shipping. I know that the
> Transaction Log shipping does not have an automatic fail over, but it will
> move the transaction log to another server and provide another server we can
> use for reporting and in the event of a failure on the main server, we could
> use the other server until we can bring it up on line.
> What in your opinion would be a better solution, cluster or transaction log
> shipping? All of our programs will be using this data, and it is important
> to recover from a disaster like this as quickly as possible. The cost of
> clustering may be preventative, so I would like your input for those who
> have used one or both methods for pros and cons. Thanks.
> John
>
>|||After much reading and study, I think we are going to implement the Database
Mirroring option with a witness to facilitate automatic fail-over.
Operating in High-Availability with full safety and a witness server should
do it for us. The servers are connected via a gigabit connection so latency
should not be a problem. Thanks one and all for the advice.
John
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C8570CAA-676A-4FE3-963D-21F4ECAC794B@.microsoft.com...
> Just a word of caution to help manage the expectation. If your storage
> goes
> bad, you can for sure leverage certain DBMS features to alleviate the
> pain.
> But there is no magic. SQL Server offers you many good features, but the
> same
> potential storage problems won't magically go away. Due diligence is
> required
> to plan for storage disasters.
> Linchi
> "John Wright" wrote:
>> We just went through a catastrophic failure of an Oracle database. This
>> database was running on a server with a RAID 5 installed. One of the
>> disks
>> was having read/write errors. When we pulled the disk from the array to
>> have the hot spare kick in, the Oracle server failed and it took a lot of
>> effort to get it back. (I hate oracle).
>> We are moving to SQL Server 2005 and want to avoid this problem. I have
>> been asked to get the specs for a cluster. I have been reading up on the
>> clustering, but came across Transaction Log Shipping. I know that the
>> Transaction Log shipping does not have an automatic fail over, but it
>> will
>> move the transaction log to another server and provide another server we
>> can
>> use for reporting and in the event of a failure on the main server, we
>> could
>> use the other server until we can bring it up on line.
>> What in your opinion would be a better solution, cluster or transaction
>> log
>> shipping? All of our programs will be using this data, and it is
>> important
>> to recover from a disaster like this as quickly as possible. The cost of
>> clustering may be preventative, so I would like your input for those who
>> have used one or both methods for pros and cons. Thanks.
>> John
>>

New Sql Server Cluster Install

Everyone,
I'm installing SQL Server 2000 SP2 virtual server onto a Windows 2003
Cluster. The install process seems to install sql server fine on both
machines, however when the installer gets to creating the virtual resources
the install fails after about 5 to 10 minutes. I've looked at the sql logs
that are generated by the install and the only error code I see that is not 0
is an error trying to load a dll. After the install fails the installer
proceeds to uninstall all files and shortcuts from both nodes. I'm thinking
this has something to do with Windows 2003 not allowing anything less than
sp3 to start. Can anyone help clarify this for me. I've searched google and
have found many articles and kb about other issues but none so far that look
like this one. If this is caused by the sp3 issues is there a workaround or
is there a way to get an install CD of SQL Server 2000 with SP3.
Thanks!
ST
Hi
Installing sp2 is no problem unless you don't patch it to sp3a after the
install completes.
Make sure you have gone through the check lists on
http://www.microsoft.com/technet/pro.../failclus.mspx
Regards
Mike
"Shannon T." wrote:

> Everyone,
> I'm installing SQL Server 2000 SP2 virtual server onto a Windows 2003
> Cluster. The install process seems to install sql server fine on both
> machines, however when the installer gets to creating the virtual resources
> the install fails after about 5 to 10 minutes. I've looked at the sql logs
> that are generated by the install and the only error code I see that is not 0
> is an error trying to load a dll. After the install fails the installer
> proceeds to uninstall all files and shortcuts from both nodes. I'm thinking
> this has something to do with Windows 2003 not allowing anything less than
> sp3 to start. Can anyone help clarify this for me. I've searched google and
> have found many articles and kb about other issues but none so far that look
> like this one. If this is caused by the sp3 issues is there a workaround or
> is there a way to get an install CD of SQL Server 2000 with SP3.
> --
> Thanks!
> ST
|||The error I'm receiving I looks like it is during the self registration phase.
The error is as follows:
09:13:43 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
09:13:43 Process Exit Code: (0)
09:13:43 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
09:13:43 Process Exit Code: (-2147312566) Error loading type library/DLL.
|||this seems to be the tsql debugger. Please refer to
http://support.microsoft.com/default...b;en-us;280101 for some
information on this.
Unless you are running tsql debugger in your clustered (production?)
environment, I doubt you would need this.
What components are you selecting in your install? Are you installing the
developers resources and code samples? It seems to me that this component is
probably installed with them as opposed to the default installation set.
"Shannon T." <ShannonT@.discussions.microsoft.com> wrote in message
news:E753DEF8-46B7-408E-BBCB-E6FE3A6A14D1@.microsoft.com...
> The error I'm receiving I looks like it is during the self registration
> phase.
> The error is as follows:
> 09:13:43 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
> 09:13:43 Process Exit Code: (0)
> 09:13:43 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
> 09:13:43 Process Exit Code: (-2147312566) Error loading type library/DLL.
>
>
|||I choose the default installation radio button on the Select Type window
during the setup. Should I use the custom install type for a virtual server?
"Hilary Cotter" wrote:

> this seems to be the tsql debugger. Please refer to
> http://support.microsoft.com/default...b;en-us;280101 for some
> information on this.
> Unless you are running tsql debugger in your clustered (production?)
> environment, I doubt you would need this.
> What components are you selecting in your install? Are you installing the
> developers resources and code samples? It seems to me that this component is
> probably installed with them as opposed to the default installation set.
> "Shannon T." <ShannonT@.discussions.microsoft.com> wrote in message
> news:E753DEF8-46B7-408E-BBCB-E6FE3A6A14D1@.microsoft.com...
>
>
|||I have removed the sql debug tools from the install. The error that was
showing up is no longer occuring. However, I still receive a message that the
installation has failed and the install rolls back.
I'm totally confused. Here is the log if anyone sees anything wrong please
let me know.
14:40:20 Begin Setup
14:40:20 8.00.194
14:40:20 Mode = Silent
14:40:20 ModeType = CLUSTER
14:40:20 Cluster node.
14:40:20 g_szIssPath=C:\WINDOWS\setup~0.iss
14:40:20 GetDefinitionEx returned: 0, Extended: 0x0
14:40:20 ValueFTS returned: 1
14:40:20 ValuePID returned: 1
14:40:20 ValueLic returned: 1
14:40:20 System: Windows NT Enterprise Server
14:40:20 SQL Server ProductType: Enterprise Edition [0x3]
14:40:20 IsNTCluster returned: 1
14:40:20 Begin Action: SetupInitialize
14:40:20 End Action SetupInitialize
14:40:20 Begin Action: SetupInstall
14:40:20 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
14:40:20 CommonFilesDir=C:\Program Files\Common Files
14:40:20 Windows Directory=C:\WINDOWS\
14:40:20 Program Files=C:\Program Files\
14:40:20 TEMPDIR=C:\DOCUME~1\username\LOCALS~1\Temp\
14:40:20 Begin Action: SetupInstall
14:40:20 digpid size : 256
14:40:20 digpid size : 164
14:40:20 Begin Action: CheckFixedRequirements
14:40:20 Platform ID: 0xf00000
14:40:20 Version: 5.2.3790
14:40:20 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.186
14:40:20 End Action: CheckFixedRequirements
14:40:20 Begin Action: ShowDialogs
14:40:20 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
14:40:20 Begin Action ShowDialogsHlpr: 0x1
14:40:20 Begin Action: DialogShowSdWelcome
14:40:20 End Action DialogShowSdWelcome
14:40:20 Dialog 0x1 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
14:40:20 Begin Action ShowDialogsHlpr: 0x2
14:40:20 Begin Action: DialogShowSdMachineName
14:40:20 [DlgMachine]
14:40:20 Result = 1
14:40:20 Type = 268435466
14:40:20 Name = virtualserver1
14:40:20 ShowDlgMachine returned: 1
14:40:20 Name = virtualserver1, Type = 0x1000000a
14:40:20 Begin Action: CheckRequirements
14:40:20 Processor Architecture: x86 (Pentium)
14:40:20 ComputerName: virtualserver1
14:40:20 User Name: username
14:40:20 IsAllAccessAllowed returned: 1
14:40:20 OS Language: 0x409
14:40:20 End Action CheckRequirements
14:40:20 This combination of Package and Operating System allows a full
product install.
14:40:20 End Action DialogShowSdMachineName
14:40:20 begin ShowDialogsUpdateMask
14:40:20 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
14:40:20 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1
14:40:20 Dialog 0x2 returned: 0
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
14:40:20 Begin Action ShowDialogsHlpr: 0x4
14:40:20 Begin Action: DialogShowSdInstallMode
14:40:20 [DlgInstallMode]
14:40:20 Result = 1
14:40:20 Type = 1
14:40:20 InstallMode : 0x1
14:40:20 End Action DialogShowSdInstallMode
14:40:20 begin ShowDialogsUpdateMask
14:40:20 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1
14:40:20 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:20 Dialog 0x4 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
14:40:20 Begin Action ShowDialogsHlpr: 0x10
14:40:20 Begin Action: DialogShowSdRegisterUserEx
14:40:20 End Action DialogShowSdRegisterUserEx
14:40:20 begin ShowDialogsUpdateMask
14:40:20 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1
14:40:20 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:20 Dialog 0x10 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
14:40:20 Begin Action ShowDialogsHlpr: 0x20
14:40:20 Begin Action: DialogShowSdLicense
14:40:20 End Action DialogShowSdLicense
14:40:20 Dialog 0x20 returned: 1
14:40:20 End Action ShowDialogsHlpr
14:40:20 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
14:40:20 Begin Action ShowDialogsHlpr: 0x4000
14:40:20 Begin Action: DialogShowSdVirtualServer
14:40:20 [DlgVirtServer]
14:40:20 Result = 1
14:40:20 VirtServerName = virtualserver
14:40:20 IpAddresses = 10.130.19.135,255.255.252.0,Public
14:40:24 ShowDlgVirtualServer returned: 0
14:40:24 Ipaddress = 10.130.19.135,255.255.252.0,Public
14:40:24 szNewList = 10.130.19.135,255.255.252.0,Public
14:40:24 szModifiedList =
14:40:24 szRemovedList =
14:40:24 End Action DialogShowSdVirtualServer
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x4000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
14:40:24 Begin Action ShowDialogsHlpr: 0x8000
14:40:24 Begin Action : DialogShowSdDiskGroups
14:40:24 [DlgDiskGroups]
14:40:24 Result = 1
14:40:24 DiskGroupsName = SQLGroup
14:40:24 ShowDlgDiskGroups returned: 1
14:40:24 Disk Group = SQLGroup
14:40:24 End Action : DialogShowSdDiskGroups
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x8000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
14:40:24 Begin Action ShowDialogsHlpr: 0x10000
14:40:24 Begin Action: DialogShowSdClusterDef
14:40:24 [DlgClusterDef]
14:40:24 Result = 1
14:40:24 nNumNodes = 2
14:40:24 VirtServerName = virtualserver
14:40:24 szPrefowners = virtualserver1,virtualserver2
14:40:24 ShowDlgClusterDef returned: 1
14:40:24 PrefOwners = virtualserver1,virtualserver2, NumIp = 0
14:40:24 End Action DialogShowSdClusterDef
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x10000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
14:40:24 Begin Action ShowDialogsHlpr: 0x20000
14:40:24 Begin Action : Cluster Security - DlgAcct
14:40:24 [DlgAccount]
14:40:24 Result = 1
14:40:24 Domain = TMC
14:40:24 DomainAcct = username
14:40:24 DomainPwd
14:40:24 ValidateUser returned: 1, 0, 0x17c
14:40:24 IsAcctValidForCluster returned: 1, 0
14:40:24 End Action : Cluster Security - DlgAcct
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
14:40:24 Dialog 0x20000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
14:40:24 Begin Action ShowDialogsHlpr: 0x40000
14:40:24 Begin Action: DialogShowSdCliSvr
14:40:24 DisplaySystemPreReq
14:40:24 [DlgClientServer]
14:40:24 Result = 1
14:40:24 Type = 2
14:40:24 ShowDlgClientServerSelect returned: 1
14:40:24 Type : 0x2
14:40:24 End Action DialogShowSdCliSvr
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bf7c037, nCurrent = 0x40000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:24 Dialog 0x40000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
14:40:24 Begin Action ShowDialogsHlpr: 0x80000
14:40:24 Begin Action: DialogShowSdInstanceName
14:40:24 [DlgInstanceName]
14:40:24 Result = 1
14:40:24 InstanceName = MSSQLSERVER
14:40:24 Begin Action: ShowDlgInstanceName
14:40:24 End Action: ShowDlgInstanceName
14:40:24 ShowDlgInstanceName returned : 1
14:40:24 InstanceName : MSSQLSERVER
14:40:24 CreateSetupTopology(virtualserver1), Handle : 0x1453f00, returned : 0
14:40:24 CreateSetupTopology returned : 0, Handle : 0x1453f00
14:40:24 Topology Type : 1, Return Value : 0
14:40:24 ST_GetPhysicalNode returned : 0, PNHandle : 0x1453f50
14:40:24 PN_EnumerateEx returned : 0
14:40:24 PN_GetSQLStates returned : 0, SqlStates : 0x0
14:40:24 PN_StartScan [0x1453f50] returned : 0
14:40:24 PN_GetNext [0x1453f50] returned : 18, Handle: [0x0]
14:40:24 No more items in enumeration.
14:40:24 ReleaseSetupTopology
14:40:24 End Action DialogShowSdInstanceName
14:40:24 begin ShowDialogsUpdateMask
14:40:24 nFullMask = 0x1bffc037, nCurrent = 0x80000, nDirection = 1
14:40:24 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:24 Dialog 0x80000 returned: 1
14:40:24 End Action ShowDialogsHlpr
14:40:24 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
14:40:24 Begin Action ShowDialogsHlpr: 0x100000
14:40:24 Begin Action: DialogShowSdSetupType
14:40:24 Begin Action: Setup Type
14:40:24 [SetupTypeSQL]
14:40:24 Result = 303
14:40:24 szDir = C:\Program Files\Microsoft SQL Server
14:40:24 final szDir = C:\Program Files\Microsoft SQL Server
14:40:24 szDataDir = g:\dbfiles
14:40:25 final szDataDir = g:\dbfiles
14:40:25 End Action: Setup Type
14:40:25 Setup Type: Custom (303)
14:40:25 End Action DialogShowSdSetupType
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x100000, nDirection = 303
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x100000 returned: 303
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x200000,index=21
14:40:25 Begin Action ShowDialogsHlpr: 0x200000
14:40:25 Begin Action: DialogShowSdComponentMult
14:40:25 basesys = 0, baseinst = 0, basedata = 0
14:40:25 Begin Action: Component Handler
14:40:25 ***** Silent Mode in Multi comps
14:40:25 [SQLComponentMult]
14:40:25 Result = 1
14:40:25 ComponentSelectItem(MgtTool\Wzcnflct): -103
14:40:25 End Action: Component Handler
14:40:25 End Action DialogShowSdComponentMult
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x200000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x200000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
14:40:25 Begin Action ShowDialogsHlpr: 0x400000
14:40:25 Begin Action: DlgServices
14:40:25 [DlgServices]
14:40:25 Result = 1
14:40:25 Local-Domain = 61680
14:40:25 AutoStart = 0
14:40:25 SQLDomain= TMC
14:40:25 SQLDomainAcct = bob
14:40:25 SQLDomainPwd
14:40:25 ValidateUser returned: 1, 0, 0x17c
14:40:25 GrantRightAsService returned : 1, 0
14:40:25 AgtDomain= TMC
14:40:25 AgtDomainAcct= bob
14:40:25 AgtDomainPwd
14:40:25 ValidateUser returned: 1, 0, 0x180
14:40:25 GrantRightAsService returned : 1, 0
14:40:25 End Action DlgServices
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x400000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x400000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
14:40:25 Begin Action ShowDialogsHlpr: 0x800000
14:40:25 Begin Action: DlgSQLSecurity
14:40:25 [DlgSQLSecurity]
14:40:25 Result = 1
14:40:25 szPwd
14:40:25 ShowDlgSQLSecurity returned: 1
14:40:25 LoginMode = 2,szPwd
14:40:25 End Action DlgSQLSecurity
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x800000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x800000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
14:40:25 Begin Action ShowDialogsHlpr: 0x1000000
14:40:25 Begin Action: DlgCollation
14:40:25 [DlgCollation]
14:40:25 Result = 1
14:40:25 collation_name = SQL_Latin1_General_CP1_CI_AS
14:40:25 ShowDlgCollation returned: 1
14:40:25 collation_name = SQL_Latin1_General_CP1_CI_AS,locale_name = ,lcid =
0x0,SortId = 0,dwCompFlags = 0x0
14:40:25 End Action DlgCollation
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x1000000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x1000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
14:40:25 Begin Action ShowDialogsHlpr: 0x2000000
14:40:25 Begin Action: DlgNetwork
14:40:25 Result = 1
14:40:25 [DlgServerNetwork]
14:40:25 NetworkLibs = 255
14:40:25 TCPPort =1433
14:40:25 TCPPrxy =
14:40:25 NMPPipeName =\\.\pipe\sql\query
14:40:25 ShowDlgNetwork returned: 1
14:40:25 [DlgServerNetwork]
14:40:25 NetworkLibs = 255
14:40:25 TCPPort = 1433
14:40:25 TCPPrxy = Default
14:40:25 NMPPipeName = \\.\pipe\sql\query
14:40:25 Result = 1
14:40:25 End Action DlgNetwork
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x2000000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x2000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
14:40:25 Begin Action ShowDialogsHlpr: 0x8000000
14:40:25 Begin Action: DialogShowSdStartCopy
14:40:25 End Action DialogShowSdStartCopy
14:40:25 begin ShowDialogsUpdateMask
14:40:25 nFullMask = 0x1bffc037, nCurrent = 0x8000000, nDirection = 1
14:40:25 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
14:40:25 Dialog 0x8000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
14:40:25 Begin Action ShowDialogsHlpr: 0x10000000
14:40:25 Begin Action: DialogShowSdLicenseMode
14:40:25 LicenseMode as read from ISS file : PERDEVICE
14:40:25 LicenseLimit as read from ISS file : 2
14:40:25 ShowDlgLicense returned: 1
14:40:25 ShowDlgLicense returned: LicenseMode = 0, LicenseLimit = 2
14:40:25 End Action DialogShowSdLicenseMode
14:40:25 Dialog 0x10000000 returned: 1
14:40:25 End Action ShowDialogsHlpr
14:40:25 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
14:40:25 End Action ShowDialogs
14:40:25 Begin Action ProcessBeforeDataMove:
14:40:25 DeinstallStart returned (C:\Program Files\Microsoft SQL
Server\MSSQL): 0
14:40:25 End Action ProcessBeforeDataMove:
14:40:25 Begin Action SetToolsComponentSelection:
14:40:25 CreateSetupTopology(virtualserver1), Handle : 0x1453f00, returned : 0
14:40:25 CreateSetupTopology returned : 0, Handle : 0x1453f00
14:40:25 Topology Type : 1, Return Value : 0
14:40:25 ST_GetPhysicalNode returned : 0, PNHandle : 0x1453f50
14:40:25 PN_EnumerateEx returned : 0
14:40:25 PN_GetSQLStates returned : 0, SqlStates : 0x0
14:40:25 PN_StartScan [0x1453f50] returned : 0
14:40:25 PN_GetNext [0x1453f50] returned : 18, Handle: [0x0]
14:40:25 No more items in enumeration.
14:40:25 ReleaseSetupTopology
14:40:25 End Action SetToolsComponentSelection:
14:40:25 Begin Action ProcessComponentSelection:
14:40:25 End Action ProcessComponentSelection
14:40:25 Begin Action LogSelectedComponents:
...
14:40:25 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:40:25 End Action LogSelectedComponents
14:40:25 SQL program folder: C:\Program Files\Microsoft SQL Server\MSSQL
14:40:25 SQL data folder: g:\dbfiles\MSSQL
14:40:25 Windows system folder: C:\WINDOWS\system32\
14:40:25 Prog req: 21962, Data req: 31360, Sys req: 60946
14:40:25 Prog avail: 5778608, Data avail: 560472816, Sys avail: 5778608
14:40:25 Prog req vs. avail, 82908, 5778608
14:40:25 Data req vs. avail, 31360, 560472816
14:40:25 Sys req vs. avail, 60946, 5778608
14:40:25 DisplaySystemPreReq
14:40:25 Begin Action InstallPkgs:
14:40:25 Begin Action: Locked Connectivity Files Check
14:40:26 ConnectivityLocked returned: 0
14:40:26 The operation completed successfully.
14:40:26 End Action: Locked Connectivity Files Check
14:40:26 Setup is installing Microsoft Data Access Components (MDAC) ...
14:40:26 C:\SQL2000_Ent\x86\Other\sqlredis.exe /q:a
14:40:33 ExitCode: 0
14:40:33 InstallMSSearch instance: MSSQLSERVER
14:40:33 Software\Microsoft\Search\Install:Version not present
14:40:33 MSSearch 2.0 or greater version check returned -1
14:40:33 Setup is installing the Microsoft Full-Text Search Engine ...
14:40:33 "C:\SQL2000_Ent\x86\FullText\MSSearch\Search\Searc hStp.exe" /s
/a:SQLServer
14:40:42 Process Exit Code: (0)
14:41:03 End Action InstallPkgs
14:41:03 Begin Action MoveFileData:
14:41:03 Enabled SELFREGISTERBATCH
14:41:03 Enabled CORECOMPONENTHANDLING
14:41:25 Begin Action: MoveFileDataSpecial
14:41:25 End Action: MoveFileDataSpecial
14:41:25 End Action MoveFileData
14:41:25 Begin Action ProcessAfterDataMove:
14:41:25 End Action ProcessAfterDataMove
14:41:25 Begin Action BuildServer:
14:41:25 C:\DOCUME~1\Username\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent 1
-Action 5 -ExePath "C:\Program Files\Microsoft SQL
Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
14:41:25 Process Exit Code: (0)
14:41:25 Begin Action: CreateRegistrySetSQL
14:41:25 End Action: CreateRegistrySetSQL
14:41:25 Begin Action: RegWriteSetupEntry
14:41:25 End Action: RegWriteSetupEntry
14:41:25 Begin Action: CreateSer
14:41:25 End Action: CreateSer
14:41:25 Begin Action: SkuIt
14:41:25 End Action: SkuIt
14:41:25 SetFileSecuritySQLAndAdmin for g:\dbfiles\MSSQL returned: 0, 0
14:41:26 SetFileSecuritySQLAndAdmin for C:\Program Files\Microsoft SQL
Server\MSSQL returned: 0, 0
14:41:26 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
14:41:26 Begin Action: UpdateSystemPath
14:41:26 Path successfully updated.
14:41:26 C:\Program
Files\EMC\PowerPath\;%SystemRoot%\system32;%System Root%;%SystemRoot%\System32\Wbem;C:\Program
Files\Dell\OpenManage\Array Manager;C:\Program Files\Microsoft SQL
Server\80\Tools\BINN
14:41:26 End Action: UpdateSystemPath
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:26 Grant Right for TMC\bob returned : 1, 0
14:41:27 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F
"C:\WINDOWS\sqlstp9.log" -I MSSQLSERVER -V 1 -M 0 -Q
"SQL_Latin1_General_CP1_CI_AS" -H 524590 -U sa -P
#####################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=virtualserver1;UID=sa;PWD=;database =master
Configuring Server ...
EXEC sp_grantlogin N'BUILTIN\Administrators'
[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'BUILTIN\Administrators'.
EXEC sp_addsrvrolemember N'BUILTIN\Administrators', 'sysadmin'
[Microsoft][ODBC SQL Server Driver][SQL Server]'BUILTIN\Administrators'
added to role 'sysadmin'.
update master.dbo.spt_server_info set attribute_value = @.@.version where
attribute_id = 2
EXEC sp_grantlogin N'TMC\bob'
[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to
'TMC\bob'.
EXEC sp_addsrvrolemember N'TMC\bob', 'sysadmin'
[Microsoft][ODBC SQL Server Driver][SQL Server]'TMC\bob' added to role
'sysadmin'.
EXEC sp_addserver N'virtualserver1', local
[Microsoft][ODBC SQL Server Driver][SQL Server]Password changed.
EXEC sp_configure 'allow updates', 1
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If
DBCC printed error messages, contact your system administrator.
[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option 'allow
updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
reconfigure with override
update master.dbo.sysaltfiles set size=1024 where name=N'tempdev'
EXEC sp_configure 'allow updates', 0
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If
DBCC printed error messages, contact your system administrator.
[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option 'allow
updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
reconfigure with override
Disconnecting from Server ...
Stopping Service ...
SQL Server has been successfully configured!
################
14:42:22 Process Exit Code: (0)
14:42:22 End Action BuildServer
14:42:22 Begin Action SelfRegiser
14:42:22 DLLRegisterServer atl.dll: 0, 0x0
14:42:27 Manual DLLRegisterServer C:\Program Files\Common Files\Microsoft
Shared\Database Replication\Conflict Viewer\wzcnf.dll: 0, 0x0
14:42:27 Begin Action SelfRegisterOnCluster
14:42:27 End Action SelfRegisterOnCluster
14:42:27 Begin Action RegisterSvrReplFiles
14:42:27 End Action RegisterSvrReplFiles
14:42:27 Begin Action SelfRegisterCOMShared
14:42:27 End Action SelfRegisterCOMShared
14:42:27 End Action SelfRegister
14:42:27 Begin Action SetupRegistry:
14:42:27 SNMP service has been detected.
14:42:27 Begin Action RegWriteInstalledInstances:
14:42:27 End Action RegWriteInstalledInstances
14:42:27 Register this installation of SQL Server with MDAC
14:42:27 Completed registering this installation of SQL Server with MDAC
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\SQLServerAgent returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\Replication returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\Providers returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for Software\Microsoft\MSSQLServer\Setup
returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for
Software\Microsoft\MSSQLServer\Tracking returned: 0, 0
14:42:27 Updating SQL Licensing Control Panel information
14:42:27 Done updating SQL Licensing Control Panel information
14:42:27 SetRegSecuritySQLAndAdmin for
System\CurrentControlset\Services\MSSQLSERVER returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for Software\Microsoft\Windows
NT\CurrentVersion\Perflib returned: 0, 0
14:42:27 SetRegSecuritySQLAndAdmin for SOFTWARE\Clients\Mail returned: 0, 0
14:42:27 End Action SetupRegistry
14:42:27 Begin Action PostSetupRegistry:
14:42:27 C:\DOCUME~1\Username\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent 1
-Action 7 -Service MSSQLSERVER -SvcStartType 1 -SvcAccount "TMC\bob" -SvcEPwd
14:42:27 Process Exit Code: (0)
14:42:27 C:\DOCUME~1\Username\LOCALS~1\Temp\SqlSetup\Bin\sc m.exe -Silent 1
-Action 5 -Service "SQLSERVERAGENT" -Dependencies MSSQLSERVER -ExePath
"C:\Program Files\Microsoft SQL Server\MSSQL\binn\sqlagent.exe" -SvcAccount
"TMC\bob" -SvcEPwd
14:42:33 Process Exit Code: (0)
14:42:33 SetupSQLExecSecurity returned: 0
14:42:33 PerfmonLoad returned: 0
14:42:33 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
14:42:33 Process Exit Code: (0)
14:42:33 MSSearch ApplicationName: SQLServer
14:42:33 C:\SQL2000_Ent\x86\FullText\ftsetup.exe SQLServer TMC\bob 1 0 1 0
14:42:33 C:\SQL2000_Ent\x86\FullText\ftsetup.exe SQLServer TMC\bob 1 0 1 0
14:42:33 Process Exit Code: (0)
14:42:33 FulltextSetup returned: 0
14:42:33 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe
-i -lcid 1033
14:42:33 Process Exit Code: (0)
14:42:33 End Action PostSetupRegistry
14:42:33 Begin Action SetupFolders:
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Enterprise Manager
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Enterprise Manager
14:42:33 Tracking\Shortcuts\Enterprise Manager
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Query Analyzer
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Query Analyzer
14:42:33 Tracking\Shortcuts\Query Analyzer
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Profiler
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Profiler
14:42:33 Tracking\Shortcuts\Profiler
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Client Network Utility
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Client Network
Utility
14:42:33 Tracking\Shortcuts\Client Network Utility
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Configure SQL XML Support in IIS
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Configure SQL XML
Support in IIS
14:42:33 Tracking\Shortcuts\Configure SQL XML Support in IIS
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Import and Export Data
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Import and Export
Data
14:42:33 Tracking\Shortcuts\Import and Export Data
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Service Manager
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Service Manager
14:42:33 Tracking\Shortcuts\Service Manager
14:42:33 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Server Network Utility
14:42:33 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Server Network
Utility
14:42:33 Tracking\Shortcuts\Server Network Utility
14:42:33 Microsoft SQL Server Folder refreshed.
14:42:33 End Action SetupFolders
14:42:33 Action CleanUpInstall:
14:42:33 Uninstall command: C:\WINDOWS\IsUninst.exe -f"C:\Program
Files\Microsoft SQL Server\MSSQL\Uninst.isu" -c"C:\Program Files\Microsoft
SQL Server\MSSQL\sqlsun.dll" -msql.mif i=MSSQLSERVER
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA4-5A21-11d2-9DAD-00C04F79D434}
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{6DC86044-0C71-11d3-9E18-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434}
14:42:33 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434} (1)
14:42:33
Software\Microsoft\MSSQLServer\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:42:33 StatsGenerate returned: 2
14:42:33 StatsGenerate (0x0,0x1,0xf00000,0x0,1033,303,0x0,0x1000000a,0,0, 0
14:42:33 StatsGenerate -1,username)
14:42:33 Installation Succeeded
|||Figured out the problem. I had taken the MSDTC offline per a step-by-step
provided by a sql server website. This was incorrect in my situation. Once I
brought the MSDTC online the install was successful. Additionally to apply
SP3 I had to manually bring the sql virtual server online before running the
sp3 setup.
Thanks to everyone that helped!

New SQL Server 2005 instance

Hi,

I am trying to install a new SQL Server 2005 instance. When running thesetup I get a warning related to "Edition Change Check" that advisesme to run setup with SKUUPGRADE=1. I already have SQL 2005 with SP 1 installed.For the new instance that I am trying to install I use the SQL Server 2005media without sp1. What do I do? Ignore the warning and at the end reapply SP1?

Thanks

The rule thumb with SQL Server installations ignore all Windows questions just answer those relevant to you. And it is better to install the service pack after the installation just download it before you install and copy your CD content into the harddrive and run setup from the harddrive. Hope this helps.|||

Sometimes is good to do just that. I have installed the newinstance and then installed the SP1 only for the new instance. There are somecheckboxes there and also you get the current version of the instance. Cool...

sql

new SQL Server 2005 install giving login error... HELP!

I completely uninstalled 2000 and did a clean install of 2005. I restored m
y
database and users and all seems fine. I am set up with mixed authenticatio
n
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40Hi
This sounds like you have orphaned users
121120120" target="_blank">http://support.microsoft.com/defaul...r />
121120120
John
"SharinDenver" wrote:

> I completely uninstalled 2000 and did a clean install of 2005. I restored
my
> database and users and all seems fine. I am set up with mixed authenticat
ion
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like you have orphaned users
> 20121120120" target="_blank">http://support.microsoft.com/defaul.../>
20121120120
> John
> "SharinDenver" wrote:
>