Hello,
I have 2 questions about setting HW for SQL cluster :
1. What is best practice to set up quorum and MSDTC disk resources? I'm
interested what group of disks they should use : one dedicated to SQL logs
or one dedicated to SQL data? How one or another design can affect
performance?
2. This question I think applies and to standalone SQL servers. It is stated
in some documents that stripe size in storage can affect performance of the
system. Is there any recomendations for this when using MS SQL?
I've been browsing through MS and HP (HP hardware is used)
supports/knowledge bases and found no precise answer to my questions so
maybe here someone can point me to some resources.
Br,
Darius K.
Quorum and MSDTC should reside on their own disks. No sharing with SQL Data
or Logs. MS states to separate Quorum and MSDTC, but that really only
applies if you are running a lot of distributed transactions.
Stripe size and stripe alignment should be covered by your hardware vendor.
If the 'expert' they provide does not understand SQL server's unique
requirements, make them send you an new one. A good hint is if he wants to
make everything a large RAID5 container and slice LUNS off of it as you need
them. That works OK for a file share, it stinks for SQL.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Dakl" <dakl@.one.lt> wrote in message
news:%23DRA7GR2EHA.3092@.TK2MSFTNGP10.phx.gbl...
> Hello,
> I have 2 questions about setting HW for SQL cluster :
> 1. What is best practice to set up quorum and MSDTC disk resources? I'm
> interested what group of disks they should use : one dedicated to SQL logs
> or one dedicated to SQL data? How one or another design can affect
> performance?
> 2. This question I think applies and to standalone SQL servers. It is
stated
> in some documents that stripe size in storage can affect performance of
the
> system. Is there any recomendations for this when using MS SQL?
> I've been browsing through MS and HP (HP hardware is used)
> supports/knowledge bases and found no precise answer to my questions so
> maybe here someone can point me to some resources.
> Br,
> Darius K.
>
|||Hi
SQL Server does I/O in the database file in 8 extents of 8kb (=64kb). All
our volumes holding databases are formatted at 64kb at OS level. The EMC
hardware striping is out of our control. When I can control it, and we are
using RAID-5, I configure it to be 64kb blocks too.
Some I/O systems perform better at 32Kb blocks, others at 64kb. You need to
test to see what is best.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:#4NigkU2EHA.3708@.TK2MSFTNGP14.phx.gbl...
> Quorum and MSDTC should reside on their own disks. No sharing with SQL
Data
> or Logs. MS states to separate Quorum and MSDTC, but that really only
> applies if you are running a lot of distributed transactions.
> Stripe size and stripe alignment should be covered by your hardware
vendor.
> If the 'expert' they provide does not understand SQL server's unique
> requirements, make them send you an new one. A good hint is if he wants
to
> make everything a large RAID5 container and slice LUNS off of it as you
need[vbcol=seagreen]
> them. That works OK for a file share, it stinks for SQL.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Dakl" <dakl@.one.lt> wrote in message
> news:%23DRA7GR2EHA.3092@.TK2MSFTNGP10.phx.gbl...
logs
> stated
> the
>
|||Hi,
I know that Quorum and MSDTC should reside on their own disks. But it is not
affordable to use separate disks. So scenario is this : there are 2 disk
groups (arrays) - one with RAID1 for Logs and second one with RAID10 for
data. To what group is better to add LUNs for Quorum and MSDTC? Or maybe
there is no difference in fact?
Br,
Dakl
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%234NigkU2EHA.3708@.TK2MSFTNGP14.phx.gbl...
> Quorum and MSDTC should reside on their own disks. No sharing with SQL
Data
> or Logs. MS states to separate Quorum and MSDTC, but that really only
> applies if you are running a lot of distributed transactions.
> Stripe size and stripe alignment should be covered by your hardware
vendor.
> If the 'expert' they provide does not understand SQL server's unique
> requirements, make them send you an new one. A good hint is if he wants
to
> make everything a large RAID5 container and slice LUNS off of it as you
need[vbcol=seagreen]
> them. That works OK for a file share, it stinks for SQL.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Dakl" <dakl@.one.lt> wrote in message
> news:%23DRA7GR2EHA.3092@.TK2MSFTNGP10.phx.gbl...
logs
> stated
> the
>
|||If you can't do RAID 10 for everything, then I would put them on the RAID 1.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Dakl" <dakl@.one.lt> wrote in message
news:Ou3VNL52EHA.2192@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I know that Quorum and MSDTC should reside on their own disks. But it is
> not
> affordable to use separate disks. So scenario is this : there are 2 disk
> groups (arrays) - one with RAID1 for Logs and second one with RAID10 for
> data. To what group is better to add LUNs for Quorum and MSDTC? Or maybe
> there is no difference in fact?
> Br,
> Dakl
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:%234NigkU2EHA.3708@.TK2MSFTNGP14.phx.gbl...
> Data
> vendor.
> to
> need
> logs
>
|||I have a EMC CX500 with 1T striped Raid 10 for Data and separate 100G Raid 5
Luns for Logs, Qorum and MSDTC. This may be a little overkill but seems to
work fine under the load we put it. In testing changes to block size really
didn't appear to affect performance greatly, in production we went with 64K.
Sir Limey
"Rodney R. Fournier [MVP]" wrote:
> If you can't do RAID 10 for everything, then I would put them on the RAID 1.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://www.msmvps.com/clustering - Blog
> "Dakl" <dakl@.one.lt> wrote in message
> news:Ou3VNL52EHA.2192@.TK2MSFTNGP14.phx.gbl...
>
>
sql
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Tuesday, March 27, 2012
Wednesday, March 21, 2012
Fault tolerant distributor in merge replication and data mirroring (in SQL Server 2005/200
Cluster it. It should be a local distributor.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Josep" <jmartinez@.autec.es> wrote in message
news:OT0UAqhUIHA.5404@.TK2MSFTNGP03.phx.gbl...
> Hello!
> My customer has SQL Server 2000 with Merge Replication, implementing a
> star tipology: one publisher (also distributor) and 11 push
> subscribers.And they want to move to SQL Server 2005/2008 and have a fault
> tolerant environment.
> I've thought that probably the best is to set up data mirroring for the
> publication, but the BOL says that data mirroring is not possible for the
> distribution database. So, what's the best way to do implement a fault
> tolerant system for the distribution database? (it's not needed to be
> automatic)
> Maybe doing backups and restores quite ofter of distribution database from
> the principal to the mirror? because we have the point that in merge
> replication only changes occurs there when the replication-schema is
> changed or a new identity range is given to a subscriber (when using
> automatic identity range).
>
> Thanks in advance!
> Josep
>
>
Your English is much better than my Spanish, and IMHO extremely good!
Again I think a restore of the publisher database or the distribution
database is your best bet. If the subscribers get ahead of the
distribution database due to a restore from an earlier version of the
distribution database, the subscribers will fill in any missing data
on the publisher.
On Jan 9, 5:13 am, "Josep" <jmarti...@.autec.es> wrote:[vbcol=seagreen]
> Ok. That's the best option, but it's quite expensive and my customer doesn't
> want it. When I said fault-tolerant I didn't mean "real time recovery", I
> should better have said that the downtime recovery process should be quite
> small: less than two hours.
> As it's a Merge Replication there can be this small downtime, that's why I
> was saying doing backup/restore of distribution database... but then I don't
> know how exactly would connect the subscribers to the distribution or other
> issues that can be there and I don't know... or, if as you said, cluster is
> the only option.
> Thank you!
> Josep.
> PS: Hilary, sorry for my English :-(
> "Hilary Cotter" <hilary.cot...@.gmail.com> escribi en el mensajenews:uDoLtIiUIHA.5132@.TK2MSFTNGP02.phx.gbl. ..
>
>
>
>
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Josep" <jmartinez@.autec.es> wrote in message
news:OT0UAqhUIHA.5404@.TK2MSFTNGP03.phx.gbl...
> Hello!
> My customer has SQL Server 2000 with Merge Replication, implementing a
> star tipology: one publisher (also distributor) and 11 push
> subscribers.And they want to move to SQL Server 2005/2008 and have a fault
> tolerant environment.
> I've thought that probably the best is to set up data mirroring for the
> publication, but the BOL says that data mirroring is not possible for the
> distribution database. So, what's the best way to do implement a fault
> tolerant system for the distribution database? (it's not needed to be
> automatic)
> Maybe doing backups and restores quite ofter of distribution database from
> the principal to the mirror? because we have the point that in merge
> replication only changes occurs there when the replication-schema is
> changed or a new identity range is given to a subscriber (when using
> automatic identity range).
>
> Thanks in advance!
> Josep
>
>
Your English is much better than my Spanish, and IMHO extremely good!
Again I think a restore of the publisher database or the distribution
database is your best bet. If the subscribers get ahead of the
distribution database due to a restore from an earlier version of the
distribution database, the subscribers will fill in any missing data
on the publisher.
On Jan 9, 5:13 am, "Josep" <jmarti...@.autec.es> wrote:[vbcol=seagreen]
> Ok. That's the best option, but it's quite expensive and my customer doesn't
> want it. When I said fault-tolerant I didn't mean "real time recovery", I
> should better have said that the downtime recovery process should be quite
> small: less than two hours.
> As it's a Merge Replication there can be this small downtime, that's why I
> was saying doing backup/restore of distribution database... but then I don't
> know how exactly would connect the subscribers to the distribution or other
> issues that can be there and I don't know... or, if as you said, cluster is
> the only option.
> Thank you!
> Josep.
> PS: Hilary, sorry for my English :-(
> "Hilary Cotter" <hilary.cot...@.gmail.com> escribi en el mensajenews:uDoLtIiUIHA.5132@.TK2MSFTNGP02.phx.gbl. ..
>
>
>
>
Friday, March 9, 2012
Faster SQL Server Backups
My database is 300 GB is size using SQL Server 2000. This is a
high-availability cluster server. My present daily maintenance job backups
take approximately 4 hours to complete.
I would like to know alternatives to faster database backups without
changing the database.
Thanks,
Where to do you take the backups? Same disk as data? Over network? What RAID level? Also, consider
backup compression software. I've mentioned a few of those on my links page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,
|||Hi,
Split-Mirror Backup is the fastest method to backup the VLDB. see the link
for details:-
http://www.microsoft.com/technet/pro.../spltmirr.mspx
Thanks
Hari
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
> backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,
|||backup to multiple files (Devices).
This can speed the backup process a ton.
backups should be on own RAID Volume (RAID 1 or RAID 1+0)
IF you can afford SQL Lite-speed, then get it.
Otherwise, try a script similar to the one attached to improve current
performance
Greg Jackson
PDX, Oregon
begin 666 spFULL_DATABASE_BACKUP.SQL
M#0HO*@.T*<W!&=6QL1&%T86)A<V5"86-K=7 -"@.T*4'5R<&]S93H-"E!E<F9O
M<FUS($9U;&P@.0F%C:W5P#0H-"D%U=&AO<CH-"D=R96=O<GD@.02!*86-K<V]N
M#0H-"D1A=&4Z#0HQ,B\R,B\R,# S#0H-"E5S96%G93H-"G1A:V5S(#,@.<&%R
M86US.@.T*"41"($Y!344-"@.E,;V-A=&EO;B!&;W(@.0D%C:W5P<R H4VAO=6QD
M(&)E(&QO8V%L(&1R:79E(&%R<F%Y(&YO="!A('-H87)E*0T*"4YU;6)E<B!O
M9B!S97!E<F%T92!B86-K=7 @.9FEL97,@.=&\@.8W)E871E("A)(')E8V]M;65N
M9"!L96%V:6YG('1H:7,@.870@.-"D-"@.T*#0H-"F5X.B @.97AE8R!!9&UI;BYD
M8F\N<W!&=6QL7T1A=&%"87-E7T)A8VMU<" G0W)E9&ET;F5T)RPG1CHO3&]C
M871I;VXO)RPT( T*#0I)('5S=6%L;'D@.8W)E871E(&$@.3D57($1A=&%B87-E
M(&YA;65D(")!1$U)3B(@.;VX@.96%C:"!397)V97(N#0H-"E1H:7,@.<W!R;V,@.
M=V]U;&0@.9V\@.:6X@.=&AE($%D;6EN($1"( T**B\-"@.T*0U)%051%('!R;V-E
M9'5R92!D8F\N<W!&=6QL7T1A=&%"87-E7T)A8VM5< T*#0HH#0I 1&%T84)A
M<V5.86UE('9A<F-H87(H,3 P*2P-"D!&:6QE4&%T:"!V87)C:&%R*#(U,"DL
M#0I 3G5M8F5R3V9&:6QE<R!T:6YY:6YT#0HI#0H-"F%S( T*#0H-"F)E9VEN
M#0H-"G-E="!N;V-O=6YT(&]N#0H-"FEF($!$871A0F%S94YA;64@.;F]T(&EN
M*'-E;&5C="!N86UE(&9R;VT@.;6%S=&5R+BYS>7-D871A8F%S97,@.#0IW:71H
M*&YO;&]C:RDI#0IB96=I;@.T*<F%I<V5R<F]R("@.G)7,@.9&]E<R!N;W0@.97AI
M<W0@.87,@.82!D871A8F%S92!O;B!T:&ES('-E<G9E<B<L(#$Q+" Q+ T*0$1A
M=&%"87-E3F%M92D-"G)E='5R;B@.P*0T*96YD#0H-"FEF($!N=6UB97)/9D9I
M;&5S(&YO="!B971W965N(#$@.86YD(#@.-"F)E9VEN#0IR86ES97)R;W(@.*"=.
M=6UB97(@.;V8@.8F%C:W5P(&9I;&5S('1O(&-R96%T92!M=7-T(&)E(&)E='=E
M96X@.,2!A;F0@.."<L( T*,3$L#0HQ*0T*<F5T=7)N*# I#0IE;F0-"@.T*#0H-
M"@.D)"0T*"0D)8F5G:6X-"@.D)"0T*"0D)9&5C;&%R92! 1&%T92!V87)C:&%R
M*#4P*2P@.0'1I;64@.=F%R8VAA<B@.U,"D-"@.T*"0D)<V5T($!$871E(#T@.8V]N
M=F5R="AV87)C:&%R+&=E=&1A=&4H*2PQ,3(I#0H-"@.D)"7-E="! =&EM92 ]
M(&-A<V4@.=VAE;@.T*;&5N*&1A=&5P87)T*&AH+&=E=&1A=&4H*2DI( #T@.,2!T
M:&5N("<P)R K(&-O;G9E<G0H=F%R8VAA<B@.S,RDL#0ID871E<&%R="AH:"QG
M971D871E*"DI*0T*"0D)"0EE;'-E(&-O;G9E<G0H=F%R8VAA<B@.S,RDL#0ID
M871E<&%R="AH:"QG971D871E*"DI*2!E;F0@.*R -"@.D)"0D)8V%S92!W:&5N
M#0IL96XH9&%T97!A<G0H;6DL9V5T9&%T92@.I*2D@./2 Q('1H96X@.)S G("L@.
M8V]N=F5R="AV87)C:&%R*#,S*2P-"F1A=&5P87)T*&UI+&=E=&1A=&4H*2DI
M#0H)"0D)"65L<V4@.8V]N=F5R="AV87)C:&%R*#,S*2P-"F1A=&5P87)T*&UI
M+&=E=&1A=&4H*2DI(&5N9" -"@.T*#0H)"0ED96-L87)E($!344Q3=')I;F<@.
M=F%R8VAA<B@.U,# P*2P@.0$9I;&5.=6UB97(-"G1I;GEI;G0-"@.T*"0D)<V5T
M($!344Q3=')I;F<@./2 H)T)!0TM54"!$051!0D%312<@.*R!C:&%R*#$S*2 K
M#0I 1&%T84)A<V5.86UE("L@.)R!43R G("L@.8VAA<B@.Q,RDI#0H-"@.D)"7-E
M="! 1FEL94YU;6)E<B ](#$-"@.T*"0D)=VAI;&4@.0$9I;&5.=6UB97(@./"!
M3G5M8F5R3V9&:6QE<PT*#0H)"0EB96=I;@.T*#0H)"0ES970@.0 %-13%-T<FEN
M9R ]("@.-"@.D)"0D)"4!344Q3=')I;F<@.*R G1$E32R ])R K#0IC:&%R*#$S
M*2 K("<G)R<@.*PT*"0D)"0D)0$9I;&50871H("L@.0$1A=&%"87-E3F%M92 K
M#0HG,"<@.*R!#;VYV97)T*&-H87(H,2DL0$9I;&5.=6UB97(I("L-"@.D)"0D)
M"2=?9G5L;%\G("L@.0$1A=&4@.("L-"D!T:6UE("L@.)RY"04LG("L@.)R<G)R K
M("<L)R K(&-H87(H,3,I#0H)"0D)"2D-"@.T*"0D)<V5T($!&:6QE3G5M8F5R
M(#T@.0$9I;&5.=6UB97(@.*R Q#0H-"@.D)"65N9 T*#0H-"@.D)"7-E="! 4U%,
M4W1R:6YG(#T@.* T*"0D)"0D)0%-13%-T<FEN9R K("=$25-+(#TG("L-"F-H
M87(H,3,I("L@.)R<G)R K#0H)"0D)"0E 1FEL95!A=&@.@.*R! 1&%T84)A<V5.
M86UE("L-"B<P)R K($-O;G9E<G0H8VAA<B@.Q*2Q 1FEL94YU;6)E<BD@.*PT*
M"0D)"0D))U]F=6QL7R<@.*R! 1&%T92 @.*PT*0'1I;64@.*R G+D)!2R<@.*R G
M)R<G("L@.8VAA<B@.Q,RD@.*PT*"0D)"0D))U=)5$@.G("L@.8VAA< B@.Q,RD@.*PT*
M"0D)"0D))TE.250L)R K(&-H87(H,3,I("L-"@.D)"0D)"2=.3T9/4DU!5"PG
M("L@.8VAA<B@.Q,RD@.*PT*"0D)"0D))U-40513(#T@.,3 G#0H)"0D)"2D-"@.T*
M#0H)"0EE>&5C*$!344Q3=')I;F<I#0H-"@.D)#0H@."0D)96YD#0H-"@.T*#0H@.
8<F5T=7)N*# I#0H@.96YD#0H@.#0I'3PT*
`
end
|||In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me
|||Most certainly write your backups to local disk as a first option, disks
different from the LUNs your data and log files are resident on.
Next, regardless if you use the maintenance plans or hand code the backups,
having multiple files per filegroup will spawn parallel processes for SQL
Server to read from for the backup.
If you want both your backups and potential restores to be faster, you'll
have to hand code a job to backup the database. Back up to multiple backup
files. This will increase the disk throughput but also spawn multiple
processes if you should ever have to restore, reducing the outage time.
Finally, check out SQL Litespeed by Imceda. It allows you to create
multiple process even without multiple files as well as gives you several
compression options to keep your to disk backups more reasonably sized.
Sincerely,
Anthony Thomas
"Leythos" <void@.nowhere.lan> wrote in message
news:MPG.1d10169943fb39819898d1@.news-server.columbus.rr.com...
In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me
high-availability cluster server. My present daily maintenance job backups
take approximately 4 hours to complete.
I would like to know alternatives to faster database backups without
changing the database.
Thanks,
Where to do you take the backups? Same disk as data? Over network? What RAID level? Also, consider
backup compression software. I've mentioned a few of those on my links page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,
|||Hi,
Split-Mirror Backup is the fastest method to backup the VLDB. see the link
for details:-
http://www.microsoft.com/technet/pro.../spltmirr.mspx
Thanks
Hari
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
> backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,
|||backup to multiple files (Devices).
This can speed the backup process a ton.
backups should be on own RAID Volume (RAID 1 or RAID 1+0)
IF you can afford SQL Lite-speed, then get it.
Otherwise, try a script similar to the one attached to improve current
performance
Greg Jackson
PDX, Oregon
begin 666 spFULL_DATABASE_BACKUP.SQL
M#0HO*@.T*<W!&=6QL1&%T86)A<V5"86-K=7 -"@.T*4'5R<&]S93H-"E!E<F9O
M<FUS($9U;&P@.0F%C:W5P#0H-"D%U=&AO<CH-"D=R96=O<GD@.02!*86-K<V]N
M#0H-"D1A=&4Z#0HQ,B\R,B\R,# S#0H-"E5S96%G93H-"G1A:V5S(#,@.<&%R
M86US.@.T*"41"($Y!344-"@.E,;V-A=&EO;B!&;W(@.0D%C:W5P<R H4VAO=6QD
M(&)E(&QO8V%L(&1R:79E(&%R<F%Y(&YO="!A('-H87)E*0T*"4YU;6)E<B!O
M9B!S97!E<F%T92!B86-K=7 @.9FEL97,@.=&\@.8W)E871E("A)(')E8V]M;65N
M9"!L96%V:6YG('1H:7,@.870@.-"D-"@.T*#0H-"F5X.B @.97AE8R!!9&UI;BYD
M8F\N<W!&=6QL7T1A=&%"87-E7T)A8VMU<" G0W)E9&ET;F5T)RPG1CHO3&]C
M871I;VXO)RPT( T*#0I)('5S=6%L;'D@.8W)E871E(&$@.3D57($1A=&%B87-E
M(&YA;65D(")!1$U)3B(@.;VX@.96%C:"!397)V97(N#0H-"E1H:7,@.<W!R;V,@.
M=V]U;&0@.9V\@.:6X@.=&AE($%D;6EN($1"( T**B\-"@.T*0U)%051%('!R;V-E
M9'5R92!D8F\N<W!&=6QL7T1A=&%"87-E7T)A8VM5< T*#0HH#0I 1&%T84)A
M<V5.86UE('9A<F-H87(H,3 P*2P-"D!&:6QE4&%T:"!V87)C:&%R*#(U,"DL
M#0I 3G5M8F5R3V9&:6QE<R!T:6YY:6YT#0HI#0H-"F%S( T*#0H-"F)E9VEN
M#0H-"G-E="!N;V-O=6YT(&]N#0H-"FEF($!$871A0F%S94YA;64@.;F]T(&EN
M*'-E;&5C="!N86UE(&9R;VT@.;6%S=&5R+BYS>7-D871A8F%S97,@.#0IW:71H
M*&YO;&]C:RDI#0IB96=I;@.T*<F%I<V5R<F]R("@.G)7,@.9&]E<R!N;W0@.97AI
M<W0@.87,@.82!D871A8F%S92!O;B!T:&ES('-E<G9E<B<L(#$Q+" Q+ T*0$1A
M=&%"87-E3F%M92D-"G)E='5R;B@.P*0T*96YD#0H-"FEF($!N=6UB97)/9D9I
M;&5S(&YO="!B971W965N(#$@.86YD(#@.-"F)E9VEN#0IR86ES97)R;W(@.*"=.
M=6UB97(@.;V8@.8F%C:W5P(&9I;&5S('1O(&-R96%T92!M=7-T(&)E(&)E='=E
M96X@.,2!A;F0@.."<L( T*,3$L#0HQ*0T*<F5T=7)N*# I#0IE;F0-"@.T*#0H-
M"@.D)"0T*"0D)8F5G:6X-"@.D)"0T*"0D)9&5C;&%R92! 1&%T92!V87)C:&%R
M*#4P*2P@.0'1I;64@.=F%R8VAA<B@.U,"D-"@.T*"0D)<V5T($!$871E(#T@.8V]N
M=F5R="AV87)C:&%R+&=E=&1A=&4H*2PQ,3(I#0H-"@.D)"7-E="! =&EM92 ]
M(&-A<V4@.=VAE;@.T*;&5N*&1A=&5P87)T*&AH+&=E=&1A=&4H*2DI( #T@.,2!T
M:&5N("<P)R K(&-O;G9E<G0H=F%R8VAA<B@.S,RDL#0ID871E<&%R="AH:"QG
M971D871E*"DI*0T*"0D)"0EE;'-E(&-O;G9E<G0H=F%R8VAA<B@.S,RDL#0ID
M871E<&%R="AH:"QG971D871E*"DI*2!E;F0@.*R -"@.D)"0D)8V%S92!W:&5N
M#0IL96XH9&%T97!A<G0H;6DL9V5T9&%T92@.I*2D@./2 Q('1H96X@.)S G("L@.
M8V]N=F5R="AV87)C:&%R*#,S*2P-"F1A=&5P87)T*&UI+&=E=&1A=&4H*2DI
M#0H)"0D)"65L<V4@.8V]N=F5R="AV87)C:&%R*#,S*2P-"F1A=&5P87)T*&UI
M+&=E=&1A=&4H*2DI(&5N9" -"@.T*#0H)"0ED96-L87)E($!344Q3=')I;F<@.
M=F%R8VAA<B@.U,# P*2P@.0$9I;&5.=6UB97(-"G1I;GEI;G0-"@.T*"0D)<V5T
M($!344Q3=')I;F<@./2 H)T)!0TM54"!$051!0D%312<@.*R!C:&%R*#$S*2 K
M#0I 1&%T84)A<V5.86UE("L@.)R!43R G("L@.8VAA<B@.Q,RDI#0H-"@.D)"7-E
M="! 1FEL94YU;6)E<B ](#$-"@.T*"0D)=VAI;&4@.0$9I;&5.=6UB97(@./"!
M3G5M8F5R3V9&:6QE<PT*#0H)"0EB96=I;@.T*#0H)"0ES970@.0 %-13%-T<FEN
M9R ]("@.-"@.D)"0D)"4!344Q3=')I;F<@.*R G1$E32R ])R K#0IC:&%R*#$S
M*2 K("<G)R<@.*PT*"0D)"0D)0$9I;&50871H("L@.0$1A=&%"87-E3F%M92 K
M#0HG,"<@.*R!#;VYV97)T*&-H87(H,2DL0$9I;&5.=6UB97(I("L-"@.D)"0D)
M"2=?9G5L;%\G("L@.0$1A=&4@.("L-"D!T:6UE("L@.)RY"04LG("L@.)R<G)R K
M("<L)R K(&-H87(H,3,I#0H)"0D)"2D-"@.T*"0D)<V5T($!&:6QE3G5M8F5R
M(#T@.0$9I;&5.=6UB97(@.*R Q#0H-"@.D)"65N9 T*#0H-"@.D)"7-E="! 4U%,
M4W1R:6YG(#T@.* T*"0D)"0D)0%-13%-T<FEN9R K("=$25-+(#TG("L-"F-H
M87(H,3,I("L@.)R<G)R K#0H)"0D)"0E 1FEL95!A=&@.@.*R! 1&%T84)A<V5.
M86UE("L-"B<P)R K($-O;G9E<G0H8VAA<B@.Q*2Q 1FEL94YU;6)E<BD@.*PT*
M"0D)"0D))U]F=6QL7R<@.*R! 1&%T92 @.*PT*0'1I;64@.*R G+D)!2R<@.*R G
M)R<G("L@.8VAA<B@.Q,RD@.*PT*"0D)"0D))U=)5$@.G("L@.8VAA< B@.Q,RD@.*PT*
M"0D)"0D))TE.250L)R K(&-H87(H,3,I("L-"@.D)"0D)"2=.3T9/4DU!5"PG
M("L@.8VAA<B@.Q,RD@.*PT*"0D)"0D))U-40513(#T@.,3 G#0H)"0D)"2D-"@.T*
M#0H)"0EE>&5C*$!344Q3=')I;F<I#0H-"@.D)#0H@."0D)96YD#0H-"@.T*#0H@.
8<F5T=7)N*# I#0H@.96YD#0H@.#0I'3PT*
`
end
|||In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me
|||Most certainly write your backups to local disk as a first option, disks
different from the LUNs your data and log files are resident on.
Next, regardless if you use the maintenance plans or hand code the backups,
having multiple files per filegroup will spawn parallel processes for SQL
Server to read from for the backup.
If you want both your backups and potential restores to be faster, you'll
have to hand code a job to backup the database. Back up to multiple backup
files. This will increase the disk throughput but also spawn multiple
processes if you should ever have to restore, reducing the outage time.
Finally, check out SQL Litespeed by Imceda. It allows you to create
multiple process even without multiple files as well as gives you several
compression options to keep your to disk backups more reasonably sized.
Sincerely,
Anthony Thomas
"Leythos" <void@.nowhere.lan> wrote in message
news:MPG.1d10169943fb39819898d1@.news-server.columbus.rr.com...
In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me
Faster SQL Server Backups
My database is 300 GB is size using SQL Server 2000. This is a
high-availability cluster server. My present daily maintenance job backups
take approximately 4 hours to complete.
I would like to know alternatives to faster database backups without
changing the database.
Thanks,Where to do you take the backups? Same disk as data? Over network? What RAID level? Also, consider
backup compression software. I've mentioned a few of those on my links page:
http://www.karaszi.com/SQLServer/links.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||Hi,
Split-Mirror Backup is the fastest method to backup the VLDB. see the link
for details:-
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
Thanks
Hari
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
> backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
--
spam999free@.rrohio.com
remove 999 in order to email me|||Most certainly write your backups to local disk as a first option, disks
different from the LUNs your data and log files are resident on.
Next, regardless if you use the maintenance plans or hand code the backups,
having multiple files per filegroup will spawn parallel processes for SQL
Server to read from for the backup.
If you want both your backups and potential restores to be faster, you'll
have to hand code a job to backup the database. Back up to multiple backup
files. This will increase the disk throughput but also spawn multiple
processes if you should ever have to restore, reducing the outage time.
Finally, check out SQL Litespeed by Imceda. It allows you to create
multiple process even without multiple files as well as gives you several
compression options to keep your to disk backups more reasonably sized.
Sincerely,
Anthony Thomas
"Leythos" <void@.nowhere.lan> wrote in message
news:MPG.1d10169943fb39819898d1@.news-server.columbus.rr.com...
In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
--
spam999free@.rrohio.com
remove 999 in order to email me
high-availability cluster server. My present daily maintenance job backups
take approximately 4 hours to complete.
I would like to know alternatives to faster database backups without
changing the database.
Thanks,Where to do you take the backups? Same disk as data? Over network? What RAID level? Also, consider
backup compression software. I've mentioned a few of those on my links page:
http://www.karaszi.com/SQLServer/links.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||Hi,
Split-Mirror Backup is the fastest method to backup the VLDB. see the link
for details:-
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
Thanks
Hari
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
> backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
--
spam999free@.rrohio.com
remove 999 in order to email me|||Most certainly write your backups to local disk as a first option, disks
different from the LUNs your data and log files are resident on.
Next, regardless if you use the maintenance plans or hand code the backups,
having multiple files per filegroup will spawn parallel processes for SQL
Server to read from for the backup.
If you want both your backups and potential restores to be faster, you'll
have to hand code a job to backup the database. Back up to multiple backup
files. This will increase the disk throughput but also spawn multiple
processes if you should ever have to restore, reducing the outage time.
Finally, check out SQL Litespeed by Imceda. It allows you to create
multiple process even without multiple files as well as gives you several
compression options to keep your to disk backups more reasonably sized.
Sincerely,
Anthony Thomas
"Leythos" <void@.nowhere.lan> wrote in message
news:MPG.1d10169943fb39819898d1@.news-server.columbus.rr.com...
In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
--
spam999free@.rrohio.com
remove 999 in order to email me
Faster SQL Server Backups
My database is 300 GB is size using SQL Server 2000. This is a
high-availability cluster server. My present daily maintenance job backups
take approximately 4 hours to complete.
I would like to know alternatives to faster database backups without
changing the database.
Thanks,Where to do you take the backups? Same disk as data? Over network? What RAID
level? Also, consider
backup compression software. I've mentioned a few of those on my links page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backup
s
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||Hi,
Split-Mirror Backup is the fastest method to backup the VLDB. see the link
for details:-
http://www.microsoft.com/technet/pr...n/spltmirr.mspx
Thanks
Hari
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
> backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backup
s
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me|||Most certainly write your backups to local disk as a first option, disks
different from the LUNs your data and log files are resident on.
Next, regardless if you use the maintenance plans or hand code the backups,
having multiple files per filegroup will spawn parallel processes for SQL
Server to read from for the backup.
If you want both your backups and potential restores to be faster, you'll
have to hand code a job to backup the database. Back up to multiple backup
files. This will increase the disk throughput but also spawn multiple
processes if you should ever have to restore, reducing the outage time.
Finally, check out SQL Litespeed by Imceda. It allows you to create
multiple process even without multiple files as well as gives you several
compression options to keep your to disk backups more reasonably sized.
Sincerely,
Anthony Thomas
"Leythos" <void@.nowhere.lan> wrote in message
news:MPG.1d10169943fb39819898d1@.news-server.columbus.rr.com...
In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me
high-availability cluster server. My present daily maintenance job backups
take approximately 4 hours to complete.
I would like to know alternatives to faster database backups without
changing the database.
Thanks,Where to do you take the backups? Same disk as data? Over network? What RAID
level? Also, consider
backup compression software. I've mentioned a few of those on my links page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backup
s
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||Hi,
Split-Mirror Backup is the fastest method to backup the VLDB. see the link
for details:-
http://www.microsoft.com/technet/pr...n/spltmirr.mspx
Thanks
Hari
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
> backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
>
> Thanks,|||In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job backup
s
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me|||Most certainly write your backups to local disk as a first option, disks
different from the LUNs your data and log files are resident on.
Next, regardless if you use the maintenance plans or hand code the backups,
having multiple files per filegroup will spawn parallel processes for SQL
Server to read from for the backup.
If you want both your backups and potential restores to be faster, you'll
have to hand code a job to backup the database. Back up to multiple backup
files. This will increase the disk throughput but also spawn multiple
processes if you should ever have to restore, reducing the outage time.
Finally, check out SQL Litespeed by Imceda. It allows you to create
multiple process even without multiple files as well as gives you several
compression options to keep your to disk backups more reasonably sized.
Sincerely,
Anthony Thomas
"Leythos" <void@.nowhere.lan> wrote in message
news:MPG.1d10169943fb39819898d1@.news-server.columbus.rr.com...
In article <1C2E2810-E1A2-4707-8047-F98FBE74C009@.microsoft.com>, =?Utf-
8?B?Sm9lIEsu?= <Joe K.@.discussions.microsoft.com> says...
> My database is 300 GB is size using SQL Server 2000. This is a
> high-availability cluster server. My present daily maintenance job
backups
> take approximately 4 hours to complete.
> I would like to know alternatives to faster database backups without
> changing the database.
Not knowing your backup method, I can only suggest that you get a
couple large disk arrays, do not use the same that your database is on,
and backup to disk and then disk to tape. Backing up across a network to
a share would require at least 1GB connection to make it worth your
effort, but backup to physical disk is faster.
--
spam999free@.rrohio.com
remove 999 in order to email me
Sunday, February 26, 2012
Farms
I'm new to the architect world and I'm trying to solve a performance problem with a SQL Server cluster. But, in talking to some folks they were recommending that I write a design based on a SQL Server "farm". However, when I ask them for more information about what a "farm" is, they start to shuffle their feat!
So, what is a farm? Is it better than a cluster? Where can I find information on creating a SQL Server farm?
Many thanks!? I haven't heard the term "farm" used too much in conjunction with SQL Server installations. But there is some info in this doc (found via Google): http://www.dell.com/downloads/global/power/4q03-mis.pdf ... looks like a pretty good article, either way. -- Adam MachanicPro SQL Server 2005, available nowhttp://www..apress.com/book/bookDisplay.html?bID=457-- <Laurence Hunter@.discussions.microsoft.com> wrote in message news:44b215d6-a25e-44ac-83d8-c18517f64798@.discussions.microsoft.com...I'm new to the architect world and I'm trying to solve a performance problem with a SQL Server cluster. But, in talking to some folks they were recommending that I write a design based on a SQL Server "farm". However, when I ask them for more information about what a "farm" is, they start to shuffle their feat!So, what is a farm? Is it better than a cluster? Where can I find information on creating a SQL Server farm?Many thanks!
Friday, February 24, 2012
Failure to Install SQL Server 2005 SP1
I am trying to apply MS SQL Server 2005 SP1 onto a 2 node cluster running Windows Server 2003, but it fails for SQL and the Analysis Services components of SQL Server, the error I am getting is MSP returned 1603 for both components. I have tried rebooting the machines but still get the same issue, the only additional dependency for SQL that I have added is for a 2nd physical disk. log details are below.
Many thanks in advance for any help you can provide on this problem.
01/15/2007 12:26:26.937 ================================================================================
01/15/2007 12:26:26.953 Hotfix package launched
01/15/2007 12:26:27.703 Product discovery successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.703 SP Level check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.734 Product language check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.750 Product version check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.765 Command-line instance name check completed during the install process
01/15/2007 12:26:27.781 Baseline build check completed during the install process
01/15/2007 12:29:31.734 Attempting to install instance: MSSQLSERVER
01/15/2007 12:29:31.750 Enumerating passive cluster nodes
01/15/2007 12:29:31.765 Patching available passive node: GBCONV1A002N03
01/15/2007 12:29:31.781 Attempting to patch running passive node: GBCONV1A002N03
01/15/2007 12:29:31.796 Waiting for first successfully completed passive node
01/15/2007 12:29:31.812 Successfully created remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.859 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.921 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.953 Successfully created new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.562 Successfully saved new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.625 Successfully created scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.640 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.656 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:28.671 Scheduled task for product instance target has completed
01/15/2007 12:30:28.687 Waiting for exit code from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.718 Received exit code 0 from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.734 Result code for scheduled task for product instance target has been received
01/15/2007 12:30:33.734 Removed scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.921 Successfully removed remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.953 Remote process completed for product instance target
01/15/2007 12:30:33.968 Exit code for passive node: GBCONV1A002N03 = 0
01/15/2007 12:30:36.812 First successful passive node has been completed
01/15/2007 12:30:36.828 Attempting to install target: GBCONV1A002N01
01/15/2007 12:30:36.843 Attempting to check for locked files: sqlrun_as.msp
01/15/2007 12:30:36.890 Attempting to check for locked files: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:36.906 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\OLAP9\Logs\OLAP9_Hotfix_KB913090_sqlrun_as.msp.out
01/15/2007 12:30:41.015 MSP returned 1603: A fatal error occurred during installation.
01/15/2007 12:30:41.140 Unable to check MSP file: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:41.156 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/15/2007 12:30:41.156 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 689
01/15/2007 12:30:41.187 Attempting to finalize cluster instance: MSSQLSERVER
01/15/2007 12:30:41.203 Waiting for all running passive nodes to complete their patch
01/15/2007 12:30:41.218 All running passive nodes have completed their patch
01/15/2007 12:30:41.234 Successfully finalized cluster instance: MSSQLSERVER
01/15/2007 12:30:41.234 Failed to install instance: MSSQLSERVER
01/15/2007 12:30:41.250
01/15/2007 12:30:41.281 Product Status Summary:
01/15/2007 12:30:41.296 Product: SQL Server Native Client (64-bit)
01/15/2007 12:30:41.312 SQL Server Native Client (64-bit) (RTM ) - Success
01/15/2007 12:30:41.312
01/15/2007 12:30:41.328 Product: Setup Support Files (64-bit)
01/15/2007 12:30:41.343 Setup Support Files (64-bit) (RTM ) - Success
01/15/2007 12:30:41.359
01/15/2007 12:30:41.375 Product: Database Services (64-bit)
01/15/2007 12:30:41.390 Database Services (64-bit) (SP1 2047 ENU GBCONV1A002V03) - Failure
01/15/2007 12:30:41.406 Analysis Services (64-bit) (RTM 1399 ENU GBCONV1A002V04) - Failure
01/15/2007 12:30:41.406
01/15/2007 12:30:41.421 Product: Integration Services (64-bit)
01/15/2007 12:30:41.437 Integration Services (64-bit) (SP1 2047 ENU) - Not Applied
01/15/2007 12:30:41.453
01/15/2007 12:30:41.468 Product: MSXML 6.0 Parser (64-bit)
01/15/2007 12:30:41.484 MSXML 6.0 Parser (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.484
01/15/2007 12:30:41.515 Product: Backward Compatibility (64-bit)
01/15/2007 12:30:41.531 Backward Compatibility (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.546
01/15/2007 12:30:41.546 Product: Microsoft SQL Server VSS Writer (64-bit)
01/15/2007 12:30:41.578 Microsoft SQL Server VSS Writer (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.593
01/15/2007 12:48:34.562 Hotfix package closed
Based on the provided log file, it finishes successfully on the passive node but fails on the
01/15/2007 12:29:31.796 Waiting for first successfully completed passive node
01/15/2007 12:29:31.812 Successfully created remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.859 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.921 Successfully transferred payload to remote product instance target \\GBCONV1A002N03
01/15/2007 12:29:45.953 Successfully created new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.562 Successfully saved new scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.625 Successfully created scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.640 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:29:46.656 Successfully started scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:28.671 Scheduled task for product instance target has completed
01/15/2007 12:30:28.687 Waiting for exit code from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.718 Received exit code 0 from scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.734 Result code for scheduled task for product instance target has been received
01/15/2007 12:30:33.734 Removed scheduled task for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.921 Successfully removed remote folder for product instance target \\GBCONV1A002N03
01/15/2007 12:30:33.953 Remote process completed for product instance target
01/15/2007 12:30:33.968 Exit code for passive node: GBCONV1A002N03 = 0
01/15/2007 12:30:36.812 First successful passive node has been completed
The error is recorded in the following section. It seems that the package is corrupted. For more details, more log files should be provided for further investigation. The log files are located under %Windows%\HOTFIX\.
01/15/2007 12:30:36.843 Attempting to check for locked files: sqlrun_as.msp
01/15/2007 12:30:36.890 Attempting to check for locked files: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:36.906 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\OLAP9\Logs\OLAP9_Hotfix_KB913090_sqlrun_as.msp.out
01/15/2007 12:30:41.015 MSP returned 1603: A fatal error occurred during installation.
01/15/2007 12:30:41.140 Unable to check MSP file: \\GBCONV1A002N01\d$\bbf7e520a98fb7a70c268b90\HotFixAS\Files\sqlrun_as.msp
01/15/2007 12:30:41.156 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/15/2007 12:30:41.156 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 689
01/15/2007 12:30:41.187 Attempting to finalize cluster instance: MSSQLSERVER
01/15/2007 12:30:41.203 Waiting for all running passive nodes to complete their patch
01/15/2007 12:30:41.218 All running passive nodes have completed their patch
01/15/2007 12:30:41.234 Successfully finalized cluster instance: MSSQLSERVER
01/15/2007 12:30:41.234 Failed to install instance: MSSQLSERVER
01/15/2007 12:30:41.250
Failure to install SQL 2005 SP2 standard on cluster
Hi,
While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install
After that installation finished , but query the server version I get:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
9.00.1399.06 RTM Standard Edition
On the Visual Studion Manager Help About I get 9.00.3042
Error logs are below. Can you please tell me how can I overcome this?
TIA.
I paste here the summary and the hotfix logs of the primary node.
There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.
summary.txt:
Time: 07/29/2007 02:46:28.253
KB Number: KB921896
Machine: DB1
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: Yes
Log Location on Passive Nodes:
(DB1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
(DB2) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.1.2047 x86
Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD
Integration Services ENU SP1 9.00.2047.00 x86 STANDARD
SQL Server Native Client ENU 9.00.2047.00 x86
Client Components ENU SP1 9.1.2047 x86 STANDARD
MSXML 6.0 Parser ENU 6.00.3883.8 x86
SQLXML4 ENU 9.00.2047.00 x86
Backward Compatibility ENU 8.05.1704 x86
Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
-
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File :
Error Number : 11009
Error Description : No passive nodes were successfully patched
-
Product : Integration Services
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
Error Number : 0
Error Description :
-
Product : SQL Server Native Client
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Reboot Required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 3010
Error Description :
-
Product : Client Components
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 0
Error Description :
-
Product : MSXML 6.0 Parser
Product Version (Previous): 3883
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
-
Product : SQLXML4
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
-
Product : Backward Compatibility
Product Version (Previous): 1704
Product Version (Final) : 2004
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
-
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
-
**********************************************************************************
Summary
No passive nodes were successfully patched
Exit Code Returned: 11009
hotfix log:
I paste here only part of the file were I think I see errors (because the post fails on complete logs)
07/29/2007 02:24:37.934 ================================================================================
07/29/2007 02:24:37.949 Hotfix package launched
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:37.980 Local Computer:
07/29/2007 02:24:37.980 Target Details: DB1
07/29/2007 02:24:37.980 commonfilesdir = C:\Program Files\Common Files
07/29/2007 02:24:37.980 lcidsupportdir = f:\33a341363e4f5937131539f1\1033
07/29/2007 02:24:37.980 programfilesdir = C:\Program Files
07/29/2007 02:24:37.980 programfilesdir_wow = C:\Program Files
07/29/2007 02:24:37.980 supportdir = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 supportdirlocal = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 windir = C:\WINDOWS
07/29/2007 02:24:37.996 winsysdir = C:\WINDOWS\system32
07/29/2007 02:24:37.996 winsysdir_wow = C:\WINDOWS\SysWOW64
07/29/2007 02:24:37.996
07/29/2007 02:24:38.012 Enumerating applicable products for this patch
07/29/2007 02:24:38.027 Found Redist 2005 product definition
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:40.105 Found Redist 2005 product definition
07/29/2007 02:24:40.137 Found Redist 2005 product definition
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:56.168 Found SQL 2005 product definition
07/29/2007 02:25:00.293 Enumeration: Determining QFE level for product instance MSSQLSERVER
07/29/2007 02:25:00.309 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
07/29/2007 02:25:00.309 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
...
07/29/2007 02:30:06.090 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 3284)
07/29/2007 02:30:06.387 Locked file: C:\Program Files\microsoft sql server\90\shared\sqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 1480)
07/29/2007 02:30:58.137 Attempting to pause the 32 bit ngen queue
07/29/2007 02:30:58.902 Installing product: Redist9
07/29/2007 02:30:58.918 Installing instance: Setup Support Files
07/29/2007 02:30:58.934 Installing target: DB1
07/29/2007 02:30:58.934 Installing file: SqlSupport.msi
07/29/2007 02:30:59.027 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
07/29/2007 02:30:59.027 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:30:59.027 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.730 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:31:29.746 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.762 Copy Engine: Installed file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
07/29/2007 02:31:29.762 Installed target: DB1
07/29/2007 02:31:30.027 Installed instance: Setup Support Files
07/29/2007 02:31:30.043 Installed product: Redist9
07/29/2007 02:31:30.043 Installing product: SQL9
07/29/2007 02:31:30.043 Installing instance: MSSQLSERVER
07/29/2007 02:31:30.059 Enumerating passive cluster nodes
07/29/2007 02:31:30.574 Patching available passive node: DB2
07/29/2007 02:31:30.574 Patching passive node: DB2
07/29/2007 02:31:30.590 Waiting for first completed passive node
07/29/2007 02:31:30.934 Task Scheduler: Created remote folder for product instance target \\DB2
07/29/2007 02:31:49.387 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.402 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.574 Task Scheduler: Error, cannot create scheduled task for product instance target \\DB2
07/29/2007 02:31:50.449 Task Scheduler: Removed remote folder for product instance target \\DB2
07/29/2007 02:31:50.449 Error, remote process failed for product instance target
07/29/2007 02:31:50.449 Exit code for passive node: DB2 = 1603
07/29/2007 02:31:50.590 The following exception occurred: No passive nodes were successfully patched Date: 07/29/2007 02:31:50.590 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp Line: 3422
07/29/2007 02:31:51.449 Watson: Param1 = Unknown
07/29/2007 02:31:51.465 Watson: Param2 = 0x2b01
07/29/2007 02:31:51.465 Watson: Param3 = Unknown
07/29/2007 02:31:51.465 Watson: Param4 = 0x0
07/29/2007 02:31:51.465 Watson: Param5 = instance.cpp@.3422
07/29/2007 02:31:51.465 Watson: Param6 = Unknown
07/29/2007 02:31:51.480 Watson: Param7 = SQL9
07/29/2007 02:31:51.480 Watson: Param8 = Hotfix@.
07/29/2007 02:31:51.480 Watson: Param9 = x86
07/29/2007 02:31:51.480 Watson: Param10 = 3042
07/29/2007 02:31:51.480 Installed product: SQL9
07/29/2007 02:31:51.480 Installing product: DTS9
07/29/2007 02:31:51.496 Installing instance: Integration Services
07/29/2007 02:31:51.496 Installing target: DB1
07/29/2007 02:31:51.512 Installing file: sqlrun_dts.msp
07/29/2007 02:31:51.512 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
...
Hey, did you resolve this? I'm running into the same issue.
Thanks,
RJ
Failure to install SQL 2005 SP2 standard on cluster
Hi,
While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install
After that installation finished , but query the server version I get:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
9.00.1399.06 RTM Standard Edition
On the Visual Studion Manager Help About I get 9.00.3042
Error logs are below. Can you please tell me how can I overcome this?
TIA.
I paste here the summary and the hotfix logs of the primary node.
There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.
summary.txt:
Time: 07/29/2007 02:46:28.253
KB Number: KB921896
Machine: DB1
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: Yes
Log Location on Passive Nodes:
(DB1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
(DB2) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.1.2047 x86
Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD
Integration Services ENU SP1 9.00.2047.00 x86 STANDARD
SQL Server Native Client ENU 9.00.2047.00 x86
Client Components ENU SP1 9.1.2047 x86 STANDARD
MSXML 6.0 Parser ENU 6.00.3883.8 x86
SQLXML4 ENU 9.00.2047.00 x86
Backward Compatibility ENU 8.05.1704 x86
Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
-
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File :
Error Number : 11009
Error Description : No passive nodes were successfully patched
-
Product : Integration Services
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
Error Number : 0
Error Description :
-
Product : SQL Server Native Client
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Reboot Required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 3010
Error Description :
-
Product : Client Components
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 0
Error Description :
-
Product : MSXML 6.0 Parser
Product Version (Previous): 3883
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
-
Product : SQLXML4
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
-
Product : Backward Compatibility
Product Version (Previous): 1704
Product Version (Final) : 2004
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
-
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
-
**********************************************************************************
Summary
No passive nodes were successfully patched
Exit Code Returned: 11009
hotfix log:
I paste here only part of the file were I think I see errors (because the post fails on complete logs)
07/29/2007 02:24:37.934 ================================================================================
07/29/2007 02:24:37.949 Hotfix package launched
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:37.980 Local Computer:
07/29/2007 02:24:37.980 Target Details: DB1
07/29/2007 02:24:37.980 commonfilesdir = C:\Program Files\Common Files
07/29/2007 02:24:37.980 lcidsupportdir = f:\33a341363e4f5937131539f1\1033
07/29/2007 02:24:37.980 programfilesdir = C:\Program Files
07/29/2007 02:24:37.980 programfilesdir_wow = C:\Program Files
07/29/2007 02:24:37.980 supportdir = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 supportdirlocal = f:\33a341363e4f5937131539f1
07/29/2007 02:24:37.996 windir = C:\WINDOWS
07/29/2007 02:24:37.996 winsysdir = C:\WINDOWS\system32
07/29/2007 02:24:37.996 winsysdir_wow = C:\WINDOWS\SysWOW64
07/29/2007 02:24:37.996
07/29/2007 02:24:38.012 Enumerating applicable products for this patch
07/29/2007 02:24:38.027 Found Redist 2005 product definition
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:40.105 Found Redist 2005 product definition
07/29/2007 02:24:40.137 Found Redist 2005 product definition
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
07/29/2007 02:24:56.168 Found SQL 2005 product definition
07/29/2007 02:25:00.293 Enumeration: Determining QFE level for product instance MSSQLSERVER
07/29/2007 02:25:00.309 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
07/29/2007 02:25:00.309 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
...
07/29/2007 02:30:06.090 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 3284)
07/29/2007 02:30:06.387 Locked file: C:\Program Files\microsoft sql server\90\shared\sqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 1480)
07/29/2007 02:30:58.137 Attempting to pause the 32 bit ngen queue
07/29/2007 02:30:58.902 Installing product: Redist9
07/29/2007 02:30:58.918 Installing instance: Setup Support Files
07/29/2007 02:30:58.934 Installing target: DB1
07/29/2007 02:30:58.934 Installing file: SqlSupport.msi
07/29/2007 02:30:59.027 Copy Engine: Creating MSI install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
07/29/2007 02:30:59.027 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:30:59.027 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.730 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
07/29/2007 02:31:29.746 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.762 Copy Engine: Installed file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
07/29/2007 02:31:29.762 Installed target: DB1
07/29/2007 02:31:30.027 Installed instance: Setup Support Files
07/29/2007 02:31:30.043 Installed product: Redist9
07/29/2007 02:31:30.043 Installing product: SQL9
07/29/2007 02:31:30.043 Installing instance: MSSQLSERVER
07/29/2007 02:31:30.059 Enumerating passive cluster nodes
07/29/2007 02:31:30.574 Patching available passive node: DB2
07/29/2007 02:31:30.574 Patching passive node: DB2
07/29/2007 02:31:30.590 Waiting for first completed passive node
07/29/2007 02:31:30.934 Task Scheduler: Created remote folder for product instance target \\DB2
07/29/2007 02:31:49.387 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.402 Task Scheduler: Transferred payload to remote product instance target \\DB2
07/29/2007 02:31:49.574 Task Scheduler: Error, cannot create scheduled task for product instance target \\DB2
07/29/2007 02:31:50.449 Task Scheduler: Removed remote folder for product instance target \\DB2
07/29/2007 02:31:50.449 Error, remote process failed for product instance target
07/29/2007 02:31:50.449 Exit code for passive node: DB2 = 1603
07/29/2007 02:31:50.590 The following exception occurred: No passive nodes were successfully patched Date: 07/29/2007 02:31:50.590 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp Line: 3422
07/29/2007 02:31:51.449 Watson: Param1 = Unknown
07/29/2007 02:31:51.465 Watson: Param2 = 0x2b01
07/29/2007 02:31:51.465 Watson: Param3 = Unknown
07/29/2007 02:31:51.465 Watson: Param4 = 0x0
07/29/2007 02:31:51.465 Watson: Param5 = instance.cpp@.3422
07/29/2007 02:31:51.465 Watson: Param6 = Unknown
07/29/2007 02:31:51.480 Watson: Param7 = SQL9
07/29/2007 02:31:51.480 Watson: Param8 = Hotfix@.
07/29/2007 02:31:51.480 Watson: Param9 = x86
07/29/2007 02:31:51.480 Watson: Param10 = 3042
07/29/2007 02:31:51.480 Installed product: SQL9
07/29/2007 02:31:51.480 Installing product: DTS9
07/29/2007 02:31:51.496 Installing instance: Integration Services
07/29/2007 02:31:51.496 Installing target: DB1
07/29/2007 02:31:51.512 Installing file: sqlrun_dts.msp
07/29/2007 02:31:51.512 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB921896_sqlrun_dts.msp.log
...
Hey, did you resolve this? I'm running into the same issue.
Thanks,
RJ
Subscribe to:
Posts (Atom)