I had a working SQL Server 2005 install based on an evaluation of Windows
Server 2003 SP2 Ent. I have several other servers running MOSS 07 and WSUS.
I upgraded the SQL server machine to 2003 R2 SP2 Ent. as the evaluation had
9 days before expiry.
However after the upgrade other machines cannot connect to the databases in
SQL, yet i can connect locally using SQL server management studio, the
databases are all intact and permissions have not been changed.
Any ideas would be gratefully received as I have my A Level coursework
stored in a a sharepoint site in one of these Databases!!!!!
AdamDid you check your Windows Firewall settings in your upgraded machine?
If it's not the problem, what's the error message exactly?
--
Ekrem Ã?nsoy
"Adam Gent" <AdamGent@.discussions.microsoft.com> wrote in message
news:2997350C-2891-46FB-AC33-010DBA43C807@.microsoft.com...
>I had a working SQL Server 2005 install based on an evaluation of Windows
> Server 2003 SP2 Ent. I have several other servers running MOSS 07 and
> WSUS.
> I upgraded the SQL server machine to 2003 R2 SP2 Ent. as the evaluation
> had
> 9 days before expiry.
> However after the upgrade other machines cannot connect to the databases
> in
> SQL, yet i can connect locally using SQL server management studio, the
> databases are all intact and permissions have not been changed.
> Any ideas would be gratefully received as I have my A Level coursework
> stored in a a sharepoint site in one of these Databases!!!!!
> Adam|||windows firewall is off - i get error message when i try to access sharepoint
pages - "cannot connect to configuration database" and WSUS gives similar
error.
I can see no errrors in the application logs on the SQL server.|||Then go to SQL Server Configuration Manager and check out your protocols.
Ensure they are enabled and configured correctly.
Also, You did not mention which SQL Server Edition you have, however SQL
Server 2005 Express and Developer Editions are configured Remote Connections
disabled by default. You could check it from SQL Server Surface Area
Configuration tool.
--
Ekrem Ã?nsoy
"Adam Gent" <AdamGent@.discussions.microsoft.com> wrote in message
news:654B7ED7-35C6-4854-8DBA-128757AAC45F@.microsoft.com...
> windows firewall is off - i get error message when i try to access
> sharepoint
> pages - "cannot connect to configuration database" and WSUS gives similar
> error.
> I can see no errrors in the application logs on the SQL server.|||I have SQL Server 2005 SP2 Enterprise.
All remote protocols are enabled apart from VIA as the service wont start
with it enabled.
"Ekrem Ã?nsoy" wrote:
> Then go to SQL Server Configuration Manager and check out your protocols.
> Ensure they are enabled and configured correctly.
> Also, You did not mention which SQL Server Edition you have, however SQL
> Server 2005 Express and Developer Editions are configured Remote Connections
> disabled by default. You could check it from SQL Server Surface Area
> Configuration tool.
> --
> Ekrem Ã?nsoy
>
> "Adam Gent" <AdamGent@.discussions.microsoft.com> wrote in message
> news:654B7ED7-35C6-4854-8DBA-128757AAC45F@.microsoft.com...
> > windows firewall is off - i get error message when i try to access
> > sharepoint
> > pages - "cannot connect to configuration database" and WSUS gives similar
> > error.
> >
> > I can see no errrors in the application logs on the SQL server.
>
Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts
Thursday, March 22, 2012
Tuesday, March 20, 2012
Applying the latest 2K5 CU Patch Scare me out of it
We're late to the party, as far as rolling out SQL2K5. I would like
to *GASP* apply the latest SP2 cumulative update to the servers(looks
like CU6). We of course have not yet encountered any of the errors
that are addressed in the CU updates. The probably-not-unique-to-us
deal is this: If we encounter any of the addressed bugs in
production, without 'proactively' applying the patch, we will get into
a lot of political hot water. Yes, MS says don't apply UNTIL you
encounter an issue, but that may not fly with the higher-ups.
I think it comes down to this for us: Are these CU patches any more
or less prone to create additional issues than a SP release?Examining how 'buggy' SQL Server service packs have been since SQL 2000 SP3,
I would say that CUs can't be any worse. :-))
There are some very significant bugs fixed in the CUs though, so I would see
if Microsoft will give you 6, or at least 5. I think CU4 (build 3186') is
the latest one you can get without going through MS.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
<SqlRandall@.gmail.com> wrote in message
news:80f70278-531e-4db5-a9cf-dc0c5b5ecd81@.60g2000hsy.googlegroups.com...
> We're late to the party, as far as rolling out SQL2K5. I would like
> to *GASP* apply the latest SP2 cumulative update to the servers(looks
> like CU6). We of course have not yet encountered any of the errors
> that are addressed in the CU updates. The probably-not-unique-to-us
> deal is this: If we encounter any of the addressed bugs in
> production, without 'proactively' applying the patch, we will get into
> a lot of political hot water. Yes, MS says don't apply UNTIL you
> encounter an issue, but that may not fly with the higher-ups.
> I think it comes down to this for us: Are these CU patches any more
> or less prone to create additional issues than a SP release?|||I cuold be wrong, but I think CU4 is .3200, which is our default. Has
proven to be stable, or we have lots of really lucky customers...
--
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.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13stt3t4ijltrb4@.corp.supernews.com...
> Examining how 'buggy' SQL Server service packs have been since SQL 2000
> SP3, I would say that CUs can't be any worse. :-))
> There are some very significant bugs fixed in the CUs though, so I would
> see if Microsoft will give you 6, or at least 5. I think CU4 (build
> 3186') is the latest one you can get without going through MS.
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> <SqlRandall@.gmail.com> wrote in message
> news:80f70278-531e-4db5-a9cf-dc0c5b5ecd81@.60g2000hsy.googlegroups.com...
>> We're late to the party, as far as rolling out SQL2K5. I would like
>> to *GASP* apply the latest SP2 cumulative update to the servers(looks
>> like CU6). We of course have not yet encountered any of the errors
>> that are addressed in the CU updates. The probably-not-unique-to-us
>> deal is this: If we encounter any of the addressed bugs in
>> production, without 'proactively' applying the patch, we will get into
>> a lot of political hot water. Yes, MS says don't apply UNTIL you
>> encounter an issue, but that may not fly with the higher-ups.
>> I think it comes down to this for us: Are these CU patches any more
>> or less prone to create additional issues than a SP release?
>|||I have found the same with 3215; it is now on all of our dev, qa and
production servers. I have only installed 3228 in one development machine
so far due to time constraints.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:ue9k0zvfIHA.5996@.TK2MSFTNGP04.phx.gbl...
>I cuold be wrong, but I think CU4 is .3200, which is our default. Has
>proven to be stable, or we have lots of really lucky customers...
to *GASP* apply the latest SP2 cumulative update to the servers(looks
like CU6). We of course have not yet encountered any of the errors
that are addressed in the CU updates. The probably-not-unique-to-us
deal is this: If we encounter any of the addressed bugs in
production, without 'proactively' applying the patch, we will get into
a lot of political hot water. Yes, MS says don't apply UNTIL you
encounter an issue, but that may not fly with the higher-ups.
I think it comes down to this for us: Are these CU patches any more
or less prone to create additional issues than a SP release?Examining how 'buggy' SQL Server service packs have been since SQL 2000 SP3,
I would say that CUs can't be any worse. :-))
There are some very significant bugs fixed in the CUs though, so I would see
if Microsoft will give you 6, or at least 5. I think CU4 (build 3186') is
the latest one you can get without going through MS.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
<SqlRandall@.gmail.com> wrote in message
news:80f70278-531e-4db5-a9cf-dc0c5b5ecd81@.60g2000hsy.googlegroups.com...
> We're late to the party, as far as rolling out SQL2K5. I would like
> to *GASP* apply the latest SP2 cumulative update to the servers(looks
> like CU6). We of course have not yet encountered any of the errors
> that are addressed in the CU updates. The probably-not-unique-to-us
> deal is this: If we encounter any of the addressed bugs in
> production, without 'proactively' applying the patch, we will get into
> a lot of political hot water. Yes, MS says don't apply UNTIL you
> encounter an issue, but that may not fly with the higher-ups.
> I think it comes down to this for us: Are these CU patches any more
> or less prone to create additional issues than a SP release?|||I cuold be wrong, but I think CU4 is .3200, which is our default. Has
proven to be stable, or we have lots of really lucky customers...
--
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.
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13stt3t4ijltrb4@.corp.supernews.com...
> Examining how 'buggy' SQL Server service packs have been since SQL 2000
> SP3, I would say that CUs can't be any worse. :-))
> There are some very significant bugs fixed in the CUs though, so I would
> see if Microsoft will give you 6, or at least 5. I think CU4 (build
> 3186') is the latest one you can get without going through MS.
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> <SqlRandall@.gmail.com> wrote in message
> news:80f70278-531e-4db5-a9cf-dc0c5b5ecd81@.60g2000hsy.googlegroups.com...
>> We're late to the party, as far as rolling out SQL2K5. I would like
>> to *GASP* apply the latest SP2 cumulative update to the servers(looks
>> like CU6). We of course have not yet encountered any of the errors
>> that are addressed in the CU updates. The probably-not-unique-to-us
>> deal is this: If we encounter any of the addressed bugs in
>> production, without 'proactively' applying the patch, we will get into
>> a lot of political hot water. Yes, MS says don't apply UNTIL you
>> encounter an issue, but that may not fly with the higher-ups.
>> I think it comes down to this for us: Are these CU patches any more
>> or less prone to create additional issues than a SP release?
>|||I have found the same with 3215; it is now on all of our dev, qa and
production servers. I have only installed 3228 in one development machine
so far due to time constraints.
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:ue9k0zvfIHA.5996@.TK2MSFTNGP04.phx.gbl...
>I cuold be wrong, but I think CU4 is .3200, which is our default. Has
>proven to be stable, or we have lots of really lucky customers...
Applying SQL SP2
I installed RS 2005 on a WIN 2003 64bit. I installed the RS Database on a
remote server Win 2003 32bit/SQL 2005 with sp2. I want to install SP2 to the
Report Server/Manager site on my 64 bit machine. When running the wizard on
the 64bit machine, it wants to upgrage the RS Database installed on the
remote server, but SP2 has already been applied. Am I going to encounter any
issues if i go forward? The remote RS Database is on a production server. Is
there going to be any downtime on my production server?Keep in mind that RS 2005 can use a SQL 2000 database as well as a SQL 2005
database as the storage for its metadata/object caching. When you apply the
patch to RS it is modifying data, tables, etc in the database it uses. It is
not upgrading SQL Server to SP2. As far as downtime, it will affect RS (but
you are already affecting that since that is what you are upgrading). It
will not affect SQL Server itself.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Marvin" <Marvin@.discussions.microsoft.com> wrote in message
news:178A9EFC-E536-4D2A-BEFE-2C2A3228893E@.microsoft.com...
>I installed RS 2005 on a WIN 2003 64bit. I installed the RS Database on a
> remote server Win 2003 32bit/SQL 2005 with sp2. I want to install SP2 to
> the
> Report Server/Manager site on my 64 bit machine. When running the wizard
> on
> the 64bit machine, it wants to upgrage the RS Database installed on the
> remote server, but SP2 has already been applied. Am I going to encounter
> any
> issues if i go forward? The remote RS Database is on a production server.
> Is
> there going to be any downtime on my production server?
remote server Win 2003 32bit/SQL 2005 with sp2. I want to install SP2 to the
Report Server/Manager site on my 64 bit machine. When running the wizard on
the 64bit machine, it wants to upgrage the RS Database installed on the
remote server, but SP2 has already been applied. Am I going to encounter any
issues if i go forward? The remote RS Database is on a production server. Is
there going to be any downtime on my production server?Keep in mind that RS 2005 can use a SQL 2000 database as well as a SQL 2005
database as the storage for its metadata/object caching. When you apply the
patch to RS it is modifying data, tables, etc in the database it uses. It is
not upgrading SQL Server to SP2. As far as downtime, it will affect RS (but
you are already affecting that since that is what you are upgrading). It
will not affect SQL Server itself.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Marvin" <Marvin@.discussions.microsoft.com> wrote in message
news:178A9EFC-E536-4D2A-BEFE-2C2A3228893E@.microsoft.com...
>I installed RS 2005 on a WIN 2003 64bit. I installed the RS Database on a
> remote server Win 2003 32bit/SQL 2005 with sp2. I want to install SP2 to
> the
> Report Server/Manager site on my 64 bit machine. When running the wizard
> on
> the 64bit machine, it wants to upgrage the RS Database installed on the
> remote server, but SP2 has already been applied. Am I going to encounter
> any
> issues if i go forward? The remote RS Database is on a production server.
> Is
> there going to be any downtime on my production server?
Monday, March 19, 2012
Applying SP4
Hi,
I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
This Test Server will be made the new Production Server. I have to apply SP4
to the Test server. Do I -
First apply SP4 to the test server and then Backup system and user databases
on Production Server and restore them on the Test Server or
Do a Backup of system and user databases on Production Server, restore them
on test server and then apply SP4 on the test server?
Will there be a issue after restore on the test server as it has SP3 and the
Production Server has SP2?
Is Backup and restore a better way here in comparison to detach and attach
database?
ThanksThat all depends, what is your goal?
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply
> SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user
> databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore
> them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and
> the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
>
>|||Thanks for the response. My goal is to promote the Test Server to a Full
Production Server running SQL Server 2000 (SP4)
"Aaron Bertrand [SQL Server MVP]" wrote:
> That all depends, what is your goal?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> > Hi,
> >
> > I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> > and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> >
> > This Test Server will be made the new Production Server. I have to apply
> > SP4
> > to the Test server. Do I -
> >
> > First apply SP4 to the test server and then Backup system and user
> > databases
> > on Production Server and restore them on the Test Server or
> > Do a Backup of system and user databases on Production Server, restore
> > them
> > on test server and then apply SP4 on the test server?
> > Will there be a issue after restore on the test server as it has SP3 and
> > the
> > Production Server has SP2?
> >
> > Is Backup and restore a better way here in comparison to detach and attach
> > database?
> >
> > Thanks
> >
> >
> >
> >
>
>|||Hi
"sharman" wrote:
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
Although I don't think you will have a any major problems with the migration
from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
server and test you application, then backup the databases, upgrade the
production server to the same level before backing up the database again and
migrating them.
John|||> Thanks for the response. My goal is to promote the Test Server to a Full
> Production Server running SQL Server 2000 (SP4)
With the exact same databases on it?
I would upgrade production to SP4, take the backups, then apply SP4 to test,
and then restore the backups.
Remember to get the 2040 hotfix (and maybe even the 2187 cumulative hotfix)
if you are using AWE.|||This would help me understand Service Packs. If I apply SP4 to Test server
and then migrate databases from Production Server (running SP2) (both system
and user databases) to the Test Server,would it undo the changes done by SP4
on Test Server?
If I migrate system and user databases from Production to Test Server and
then apply SP4 to Test Server and test it. After successful testing I just
migrate the user databases to the test server, would it undo the changes done
by SP4 on Test Server?
"John Bell" wrote:
> Hi
> "sharman" wrote:
> > Hi,
> >
> > I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> > and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> >
> > This Test Server will be made the new Production Server. I have to apply SP4
> > to the Test server. Do I -
> >
> > First apply SP4 to the test server and then Backup system and user databases
> > on Production Server and restore them on the Test Server or
> > Do a Backup of system and user databases on Production Server, restore them
> > on test server and then apply SP4 on the test server?
> > Will there be a issue after restore on the test server as it has SP3 and the
> > Production Server has SP2?
> >
> > Is Backup and restore a better way here in comparison to detach and attach
> > database?
> >
> > Thanks
> Although I don't think you will have a any major problems with the migration
> from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
> server and test you application, then backup the databases, upgrade the
> production server to the same level before backing up the database again and
> migrating them.
> John|||Hi
"sharman" wrote:
> This would help me understand Service Packs. If I apply SP4 to Test server
> and then migrate databases from Production Server (running SP2) (both system
> and user databases) to the Test Server,would it undo the changes done by SP4
> on Test Server?
> If I migrate system and user databases from Production to Test Server and
> then apply SP4 to Test Server and test it. After successful testing I just
> migrate the user databases to the test server, would it undo the changes done
> by SP4 on Test Server?
>
The exact changes to a database made by a release or hotfix is not usually
made available to people outside MS, although I guess you could raise an
incident to ask. Even if the database files are compatible, if you tested on
one version the behaviour of your application will not necessarily be the
same when run on a different version, therefore invalidating your tests. It
is therefore best to upgrade in such a way as everything is in step.
HTH
John
I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
This Test Server will be made the new Production Server. I have to apply SP4
to the Test server. Do I -
First apply SP4 to the test server and then Backup system and user databases
on Production Server and restore them on the Test Server or
Do a Backup of system and user databases on Production Server, restore them
on test server and then apply SP4 on the test server?
Will there be a issue after restore on the test server as it has SP3 and the
Production Server has SP2?
Is Backup and restore a better way here in comparison to detach and attach
database?
ThanksThat all depends, what is your goal?
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply
> SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user
> databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore
> them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and
> the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
>
>|||Thanks for the response. My goal is to promote the Test Server to a Full
Production Server running SQL Server 2000 (SP4)
"Aaron Bertrand [SQL Server MVP]" wrote:
> That all depends, what is your goal?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> > Hi,
> >
> > I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> > and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> >
> > This Test Server will be made the new Production Server. I have to apply
> > SP4
> > to the Test server. Do I -
> >
> > First apply SP4 to the test server and then Backup system and user
> > databases
> > on Production Server and restore them on the Test Server or
> > Do a Backup of system and user databases on Production Server, restore
> > them
> > on test server and then apply SP4 on the test server?
> > Will there be a issue after restore on the test server as it has SP3 and
> > the
> > Production Server has SP2?
> >
> > Is Backup and restore a better way here in comparison to detach and attach
> > database?
> >
> > Thanks
> >
> >
> >
> >
>
>|||Hi
"sharman" wrote:
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
Although I don't think you will have a any major problems with the migration
from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
server and test you application, then backup the databases, upgrade the
production server to the same level before backing up the database again and
migrating them.
John|||> Thanks for the response. My goal is to promote the Test Server to a Full
> Production Server running SQL Server 2000 (SP4)
With the exact same databases on it?
I would upgrade production to SP4, take the backups, then apply SP4 to test,
and then restore the backups.
Remember to get the 2040 hotfix (and maybe even the 2187 cumulative hotfix)
if you are using AWE.|||This would help me understand Service Packs. If I apply SP4 to Test server
and then migrate databases from Production Server (running SP2) (both system
and user databases) to the Test Server,would it undo the changes done by SP4
on Test Server?
If I migrate system and user databases from Production to Test Server and
then apply SP4 to Test Server and test it. After successful testing I just
migrate the user databases to the test server, would it undo the changes done
by SP4 on Test Server?
"John Bell" wrote:
> Hi
> "sharman" wrote:
> > Hi,
> >
> > I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> > and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> >
> > This Test Server will be made the new Production Server. I have to apply SP4
> > to the Test server. Do I -
> >
> > First apply SP4 to the test server and then Backup system and user databases
> > on Production Server and restore them on the Test Server or
> > Do a Backup of system and user databases on Production Server, restore them
> > on test server and then apply SP4 on the test server?
> > Will there be a issue after restore on the test server as it has SP3 and the
> > Production Server has SP2?
> >
> > Is Backup and restore a better way here in comparison to detach and attach
> > database?
> >
> > Thanks
> Although I don't think you will have a any major problems with the migration
> from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
> server and test you application, then backup the databases, upgrade the
> production server to the same level before backing up the database again and
> migrating them.
> John|||Hi
"sharman" wrote:
> This would help me understand Service Packs. If I apply SP4 to Test server
> and then migrate databases from Production Server (running SP2) (both system
> and user databases) to the Test Server,would it undo the changes done by SP4
> on Test Server?
> If I migrate system and user databases from Production to Test Server and
> then apply SP4 to Test Server and test it. After successful testing I just
> migrate the user databases to the test server, would it undo the changes done
> by SP4 on Test Server?
>
The exact changes to a database made by a release or hotfix is not usually
made available to people outside MS, although I guess you could raise an
incident to ask. Even if the database files are compatible, if you tested on
one version the behaviour of your application will not necessarily be the
same when run on a different version, therefore invalidating your tests. It
is therefore best to upgrade in such a way as everything is in step.
HTH
John
Applying SP4
Hi,
I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
This Test Server will be made the new Production Server. I have to apply SP4
to the Test server. Do I -
First apply SP4 to the test server and then Backup system and user databases
on Production Server and restore them on the Test Server or
Do a Backup of system and user databases on Production Server, restore them
on test server and then apply SP4 on the test server?
Will there be a issue after restore on the test server as it has SP3 and the
Production Server has SP2?
Is Backup and restore a better way here in comparison to detach and attach
database?
Thanks
That all depends, what is your goal?
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply
> SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user
> databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore
> them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and
> the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
>
>
|||Thanks for the response. My goal is to promote the Test Server to a Full
Production Server running SQL Server 2000 (SP4)
"Aaron Bertrand [SQL Server MVP]" wrote:
> That all depends, what is your goal?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
>
>
|||Hi
"sharman" wrote:
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
Although I don't think you will have a any major problems with the migration
from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
server and test you application, then backup the databases, upgrade the
production server to the same level before backing up the database again and
migrating them.
John
|||> Thanks for the response. My goal is to promote the Test Server to a Full
> Production Server running SQL Server 2000 (SP4)
With the exact same databases on it?
I would upgrade production to SP4, take the backups, then apply SP4 to test,
and then restore the backups.
Remember to get the 2040 hotfix (and maybe even the 2187 cumulative hotfix)
if you are using AWE.
|||This would help me understand Service Packs. If I apply SP4 to Test server
and then migrate databases from Production Server (running SP2) (both system
and user databases) to the Test Server,would it undo the changes done by SP4
on Test Server?
If I migrate system and user databases from Production to Test Server and
then apply SP4 to Test Server and test it. After successful testing I just
migrate the user databases to the test server, would it undo the changes done
by SP4 on Test Server?
"John Bell" wrote:
> Hi
> "sharman" wrote:
>
> Although I don't think you will have a any major problems with the migration
> from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
> server and test you application, then backup the databases, upgrade the
> production server to the same level before backing up the database again and
> migrating them.
> John
|||Hi
"sharman" wrote:
> This would help me understand Service Packs. If I apply SP4 to Test server
> and then migrate databases from Production Server (running SP2) (both system
> and user databases) to the Test Server,would it undo the changes done by SP4
> on Test Server?
> If I migrate system and user databases from Production to Test Server and
> then apply SP4 to Test Server and test it. After successful testing I just
> migrate the user databases to the test server, would it undo the changes done
> by SP4 on Test Server?
>
The exact changes to a database made by a release or hotfix is not usually
made available to people outside MS, although I guess you could raise an
incident to ask. Even if the database files are compatible, if you tested on
one version the behaviour of your application will not necessarily be the
same when run on a different version, therefore invalidating your tests. It
is therefore best to upgrade in such a way as everything is in step.
HTH
John
I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
This Test Server will be made the new Production Server. I have to apply SP4
to the Test server. Do I -
First apply SP4 to the test server and then Backup system and user databases
on Production Server and restore them on the Test Server or
Do a Backup of system and user databases on Production Server, restore them
on test server and then apply SP4 on the test server?
Will there be a issue after restore on the test server as it has SP3 and the
Production Server has SP2?
Is Backup and restore a better way here in comparison to detach and attach
database?
Thanks
That all depends, what is your goal?
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply
> SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user
> databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore
> them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and
> the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
>
>
|||Thanks for the response. My goal is to promote the Test Server to a Full
Production Server running SQL Server 2000 (SP4)
"Aaron Bertrand [SQL Server MVP]" wrote:
> That all depends, what is your goal?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
>
>
|||Hi
"sharman" wrote:
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
Although I don't think you will have a any major problems with the migration
from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
server and test you application, then backup the databases, upgrade the
production server to the same level before backing up the database again and
migrating them.
John
|||> Thanks for the response. My goal is to promote the Test Server to a Full
> Production Server running SQL Server 2000 (SP4)
With the exact same databases on it?
I would upgrade production to SP4, take the backups, then apply SP4 to test,
and then restore the backups.
Remember to get the 2040 hotfix (and maybe even the 2187 cumulative hotfix)
if you are using AWE.
|||This would help me understand Service Packs. If I apply SP4 to Test server
and then migrate databases from Production Server (running SP2) (both system
and user databases) to the Test Server,would it undo the changes done by SP4
on Test Server?
If I migrate system and user databases from Production to Test Server and
then apply SP4 to Test Server and test it. After successful testing I just
migrate the user databases to the test server, would it undo the changes done
by SP4 on Test Server?
"John Bell" wrote:
> Hi
> "sharman" wrote:
>
> Although I don't think you will have a any major problems with the migration
> from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
> server and test you application, then backup the databases, upgrade the
> production server to the same level before backing up the database again and
> migrating them.
> John
|||Hi
"sharman" wrote:
> This would help me understand Service Packs. If I apply SP4 to Test server
> and then migrate databases from Production Server (running SP2) (both system
> and user databases) to the Test Server,would it undo the changes done by SP4
> on Test Server?
> If I migrate system and user databases from Production to Test Server and
> then apply SP4 to Test Server and test it. After successful testing I just
> migrate the user databases to the test server, would it undo the changes done
> by SP4 on Test Server?
>
The exact changes to a database made by a release or hotfix is not usually
made available to people outside MS, although I guess you could raise an
incident to ask. Even if the database files are compatible, if you tested on
one version the behaviour of your application will not necessarily be the
same when run on a different version, therefore invalidating your tests. It
is therefore best to upgrade in such a way as everything is in step.
HTH
John
Applying SP4
Hi,
I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
This Test Server will be made the new Production Server. I have to apply SP4
to the Test server. Do I -
First apply SP4 to the test server and then Backup system and user databases
on Production Server and restore them on the Test Server or
Do a Backup of system and user databases on Production Server, restore them
on test server and then apply SP4 on the test server?
Will there be a issue after restore on the test server as it has SP3 and the
Production Server has SP2?
Is Backup and restore a better way here in comparison to detach and attach
database?
ThanksThat all depends, what is your goal?
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply
> SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user
> databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore
> them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and
> the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
>
>|||Thanks for the response. My goal is to promote the Test Server to a Full
Production Server running SQL Server 2000 (SP4)
"Aaron Bertrand [SQL Server MVP]" wrote:
> That all depends, what is your goal?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
>
>|||Hi
"sharman" wrote:
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply S
P4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user databas
es
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore the
m
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and t
he
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
Although I don't think you will have a any major problems with the migration
from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
server and test you application, then backup the databases, upgrade the
production server to the same level before backing up the database again and
migrating them.
John|||> Thanks for the response. My goal is to promote the Test Server to a Full
> Production Server running SQL Server 2000 (SP4)
With the exact same databases on it?
I would upgrade production to SP4, take the backups, then apply SP4 to test,
and then restore the backups.
Remember to get the 2040 hotfix (and maybe even the 2187 cumulative hotfix)
if you are using AWE.|||This would help me understand Service Packs. If I apply SP4 to Test server
and then migrate databases from Production Server (running SP2) (both system
and user databases) to the Test Server,would it undo the changes done by SP4
on Test Server?
If I migrate system and user databases from Production to Test Server and
then apply SP4 to Test Server and test it. After successful testing I just
migrate the user databases to the test server, would it undo the changes don
e
by SP4 on Test Server?
"John Bell" wrote:
> Hi
> "sharman" wrote:
>
> Although I don't think you will have a any major problems with the migrati
on
> from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the tes
t
> server and test you application, then backup the databases, upgrade the
> production server to the same level before backing up the database again a
nd
> migrating them.
> John|||Hi
"sharman" wrote:
> This would help me understand Service Packs. If I apply SP4 to Test server
> and then migrate databases from Production Server (running SP2) (both syst
em
> and user databases) to the Test Server,would it undo the changes done by S
P4
> on Test Server?
> If I migrate system and user databases from Production to Test Server and
> then apply SP4 to Test Server and test it. After successful testing I just
> migrate the user databases to the test server, would it undo the changes d
one
> by SP4 on Test Server?
>
The exact changes to a database made by a release or hotfix is not usually
made available to people outside MS, although I guess you could raise an
incident to ask. Even if the database files are compatible, if you tested o
n
one version the behaviour of your application will not necessarily be the
same when run on a different version, therefore invalidating your tests. It
is therefore best to upgrade in such a way as everything is in step.
HTH
John
I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
This Test Server will be made the new Production Server. I have to apply SP4
to the Test server. Do I -
First apply SP4 to the test server and then Backup system and user databases
on Production Server and restore them on the Test Server or
Do a Backup of system and user databases on Production Server, restore them
on test server and then apply SP4 on the test server?
Will there be a issue after restore on the test server as it has SP3 and the
Production Server has SP2?
Is Backup and restore a better way here in comparison to detach and attach
database?
ThanksThat all depends, what is your goal?
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply
> SP4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user
> databases
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore
> them
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and
> the
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
>
>|||Thanks for the response. My goal is to promote the Test Server to a Full
Production Server running SQL Server 2000 (SP4)
"Aaron Bertrand [SQL Server MVP]" wrote:
> That all depends, what is your goal?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:11FCCE2A-19D0-4B26-8B71-107FB518A1AA@.microsoft.com...
>
>|||Hi
"sharman" wrote:
> Hi,
> I have a Production Server - Windows 2000 Server, SQL Server 2000 (SP2)
> and a Test server - Windows 2003 Server, SQL Server 2000 (SP3).
> This Test Server will be made the new Production Server. I have to apply S
P4
> to the Test server. Do I -
> First apply SP4 to the test server and then Backup system and user databas
es
> on Production Server and restore them on the Test Server or
> Do a Backup of system and user databases on Production Server, restore the
m
> on test server and then apply SP4 on the test server?
> Will there be a issue after restore on the test server as it has SP3 and t
he
> Production Server has SP2?
> Is Backup and restore a better way here in comparison to detach and attach
> database?
> Thanks
Although I don't think you will have a any major problems with the migration
from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the test
server and test you application, then backup the databases, upgrade the
production server to the same level before backing up the database again and
migrating them.
John|||> Thanks for the response. My goal is to promote the Test Server to a Full
> Production Server running SQL Server 2000 (SP4)
With the exact same databases on it?
I would upgrade production to SP4, take the backups, then apply SP4 to test,
and then restore the backups.
Remember to get the 2040 hotfix (and maybe even the 2187 cumulative hotfix)
if you are using AWE.|||This would help me understand Service Packs. If I apply SP4 to Test server
and then migrate databases from Production Server (running SP2) (both system
and user databases) to the Test Server,would it undo the changes done by SP4
on Test Server?
If I migrate system and user databases from Production to Test Server and
then apply SP4 to Test Server and test it. After successful testing I just
migrate the user databases to the test server, would it undo the changes don
e
by SP4 on Test Server?
"John Bell" wrote:
> Hi
> "sharman" wrote:
>
> Although I don't think you will have a any major problems with the migrati
on
> from SP2 to SP4 (plus hotfixes) the safest way would be to upgrade the tes
t
> server and test you application, then backup the databases, upgrade the
> production server to the same level before backing up the database again a
nd
> migrating them.
> John|||Hi
"sharman" wrote:
> This would help me understand Service Packs. If I apply SP4 to Test server
> and then migrate databases from Production Server (running SP2) (both syst
em
> and user databases) to the Test Server,would it undo the changes done by S
P4
> on Test Server?
> If I migrate system and user databases from Production to Test Server and
> then apply SP4 to Test Server and test it. After successful testing I just
> migrate the user databases to the test server, would it undo the changes d
one
> by SP4 on Test Server?
>
The exact changes to a database made by a release or hotfix is not usually
made available to people outside MS, although I guess you could raise an
incident to ask. Even if the database files are compatible, if you tested o
n
one version the behaviour of your application will not necessarily be the
same when run on a different version, therefore invalidating your tests. It
is therefore best to upgrade in such a way as everything is in step.
HTH
John
Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)
Hello,
I'm experiencing some issues with applying SP2. I'm getting a failure for the database engine (on two instances that have been installed on a server). I've noticed in the forum that a few others have had some issues in this area as well. The slightly strange thing is that if I check the version of SQL Server on each instance it is telling me that SP2 has been installed:
9.00.3042.00 SP2 Enterprise Edition (64-bit)
So, the logs tell me I have a failed upgrade, but SQL is telling me it has been upgraded.
Any help would be appreciated.
--
from SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Fri Jun 22 11:52:44 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (1C:98) [11:52:44:201]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:201]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 11:52:44: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
the end of that file has the following information:
MSI (s) (1C:98) [11:52:44:701]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 2 for SQL Server Database Services 2005 (64-bit) ENU (KB921896)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 1729
MSI (s) (1C:98) [11:52:44:701]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed.
MSI (s) (1C:98) [11:52:44:748]: Attempting to delete file C:\WINDOWS\Installer\3cda1ca.msp
MSI (s) (1C:98) [11:52:44:794]: Cleaning up uninstalled install packages, if any exist
MSI (s) (1C:98) [11:52:44:794]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\3cda1ca.msp'
MSI (s) (1C:98) [11:52:44:794]: MainEngineThread is returning 1603
MSI (s) (1C:94) [11:52:44:794]: Destroying RemoteAPI object.
MSI (s) (1C:BC) [11:52:44:794]: Custom Action Manager thread ending.
=== Logging stopped: 22/06/2007 11:52:44 ===
MSI (c) (60:AC) [11:52:44:841]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (60:AC) [11:52:44:841]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/06/2007 11:52:44 ===
Did you had a chance to look at
http://support.microsoft.com/default.aspx/kb/933945|||I have had a look at that but wasn't certain that it applied as it was for an earlier fix. I am thinking about trying to install the critical update for SP2 to see if that helps (http://support.microsoft.com/?kbid=934458). I haven't tried that, but am about to. If that works I will update this thread.
From Summary.txt from existing SP2 installation attempt:
-
Product : Database Services (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : Database Services (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
...and at the end of the file:
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29537
|||I tried applying the critical update for SP2 (http://support.microsoft.com/?kbid=934458).
I basically got very, very similar symptons to what I expereienced when installing SP2.
The logs tell me that the process was not successful for the database engine(s) and I am still getting different error messages per instance. Some logs are included:
-
Summary.txt
-
Product Installation Status
Product : SQL Server Database Services 2005 (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : SQL Server Database Services 2005 (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
-
SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
-
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='1802' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:43:40 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1802' GetLastError='0'>
MSI (s) (84:90) [16:43:40:476]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:476]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:43:40: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:43:40: INSTALL. Return value 3.
--
SQL9_Hotfix_KB934458_sqlrun_sql.msp_0.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:45:13 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (84:28) [16:45:13:713]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:713]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:45:13: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:45:13: INSTALL. Return value 3.
--
If I then check what version files are at, sqlservr.exe is at version 2005.90.3054.0 and Microsoft.SqlServer.MaintenancePlanTasks.dll is at version 9.0.3054.0.
select @.@.version is returning "Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)"
So does this mean that the logs are not correct and SP2 and the updates have been successfully applied?
|||Could you check the version of Binaries ? sqlservr.exe|||Associated Hotfix Build: 3159
File version: 2005.090.3054.00
Product Version: 9.00.3054.00
This is for both instances. So, it looks as though the database engine got upgraded successfully - but the logs are telling me otherwise!
|||Exactly.
Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)
Hello,
I'm experiencing some issues with applying SP2. I'm getting a failure for the database engine (on two instances that have been installed on a server). I've noticed in the forum that a few others have had some issues in this area as well. The slightly strange thing is that if I check the version of SQL Server on each instance it is telling me that SP2 has been installed:
9.00.3042.00 SP2 Enterprise Edition (64-bit)
So, the logs tell me I have a failed upgrade, but SQL is telling me it has been upgraded.
Any help would be appreciated.
--
from SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Fri Jun 22 11:52:44 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (1C:98) [11:52:44:201]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:201]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (1C:98) [11:52:44:216]: Transforming table InstallExecuteSequence.
MSI (s) (1C:98) [11:52:44:216]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 11:52:44: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
the end of that file has the following information:
MSI (s) (1C:98) [11:52:44:701]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 2 for SQL Server Database Services 2005 (64-bit) ENU (KB921896)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 1729
MSI (s) (1C:98) [11:52:44:701]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:701]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:716]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:716]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Transforming table Error.
MSI (s) (1C:98) [11:52:44:732]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:98) [11:52:44:732]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed.
MSI (s) (1C:98) [11:52:44:748]: Attempting to delete file C:\WINDOWS\Installer\3cda1ca.msp
MSI (s) (1C:98) [11:52:44:794]: Cleaning up uninstalled install packages, if any exist
MSI (s) (1C:98) [11:52:44:794]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\3cda1ca.msp'
MSI (s) (1C:98) [11:52:44:794]: MainEngineThread is returning 1603
MSI (s) (1C:94) [11:52:44:794]: Destroying RemoteAPI object.
MSI (s) (1C:BC) [11:52:44:794]: Custom Action Manager thread ending.
=== Logging stopped: 22/06/2007 11:52:44 ===
MSI (c) (60:AC) [11:52:44:841]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (60:AC) [11:52:44:841]: MainEngineThread is returning 1603
=== Verbose logging stopped: 22/06/2007 11:52:44 ===
Did you had a chance to look at
http://support.microsoft.com/default.aspx/kb/933945|||I have had a look at that but wasn't certain that it applied as it was for an earlier fix. I am thinking about trying to install the critical update for SP2 to see if that helps (http://support.microsoft.com/?kbid=934458). I haven't tried that, but am about to. If that works I will update this thread.
From Summary.txt from existing SP2 installation attempt:
-
Product : Database Services (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : Database Services (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
...and at the end of the file:
**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 29537
|||I tried applying the critical update for SP2 (http://support.microsoft.com/?kbid=934458).
I basically got very, very similar symptons to what I expereienced when installing SP2.
The logs tell me that the process was not successful for the database engine(s) and I am still getting different error messages per instance. Some logs are included:
-
Summary.txt
-
Product Installation Status
Product : SQL Server Database Services 2005 (SQL01)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
-
Product : SQL Server Database Services 2005 (SQL02)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29537
Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
-
-
SQL9_Hotfix_KB934458_sqlrun_sql.msp.log
-
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='1802' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:43:40 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1802' GetLastError='0'>
MSI (s) (84:90) [16:43:40:476]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:476]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:90) [16:43:40:492]: Transforming table InstallExecuteSequence.
MSI (s) (84:90) [16:43:40:492]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:43:40: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:43:40: INSTALL. Return value 3.
--
SQL9_Hotfix_KB934458_sqlrun_sql.msp_0.log
--
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Incorrect syntax near '='.. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='102' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Tue Jun 26 16:45:13 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='102' GetLastError='0'>
MSI (s) (84:28) [16:45:13:713]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:713]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:28) [16:45:13:728]: Transforming table InstallExecuteSequence.
MSI (s) (84:28) [16:45:13:728]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 16:45:13: CommitSqlUpgrade.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 3.
Action ended 16:45:13: INSTALL. Return value 3.
--
If I then check what version files are at, sqlservr.exe is at version 2005.90.3054.0 and Microsoft.SqlServer.MaintenancePlanTasks.dll is at version 9.0.3054.0.
select @.@.version is returning "Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)"
So does this mean that the logs are not correct and SP2 and the updates have been successfully applied?
|||Could you check the version of Binaries ? sqlservr.exe|||Associated Hotfix Build: 3159
File version: 2005.090.3054.00
Product Version: 9.00.3054.00
This is for both instances. So, it looks as though the database engine got upgraded successfully - but the logs are telling me otherwise!
|||Exactly.
applying SP to 2005 active/active cluster
I have a 2005 active/active cluster and want to apply SQL server 2005 SP2 to both node.
I know that for active/passive , the sp can simple be installed on the active node(instance) and everything will be replicated to the other node.
bear in mind what I have SSIS and SSAS and SSRS running on the active/active cluster.
I know that for active/passive , the sp can simple be installed on the active node(instance) and everything will be replicated to the other node.
bear in mind what I have SSIS and SSAS and SSRS running on the active/active cluster.
what is the rigth method for applying the SP to active\active cluster?
Thanks
We had the same situation a couple of weeks ago. When had several problems applying SP2 to the clustered machines. After talking to MS for several hrs about our problems, we finally corrected it....it was issues with different settings on our cluster. However, MS did recommend having both instances on one server, the primary, when you do the upgrade. I can't remember if the SP was applied to both nodes though. If it is not, its no big deal. Just apply it to the second node. I hope you have better luck than we did.
PS. Make sure that DCOM is enabled on both servers.
Applying service packs
Hi,
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.
I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.
I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
Applying service packs
Hi,
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new serve
r
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the curren
t
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new serve
r
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the curren
t
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
Applying service packs
Hi,
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
--
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
I have a production server running SQL 2000 SP2 on Windows 2000 server. I
have to migrate all the databases on this production server to a new server
running SQL Server 2000 SP4 on Windows 2003 Server.
Are there any known issues? How should I proceed ? Apply SP4 on the current
Production Server first and then migrate? Any insight will be greatly
appreciated. Thanks.I would recommend applying SP4 to the current server before the migration.
This way all your system databases will match between systems.
If you are going to copy the system databases as well (which I would
recommend if you can keep all the directory paths the same) you will need to
do a sp_droplogin and sp_addlogin to change the server's name to the new
server name.
There should be no issues with this migration.
--
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"sharman" wrote:
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.|||Hello,
Best option:-
1. Install SP4 to current production system
2. Copy the databases to new server.
3. You can also copy the system databases. This will ahelp you not to create
any jobs, DTS, Logins...
Thanks
Hari
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F892EF13-069B-4E8A-9DB7-0EF942C90450@.microsoft.com...
> Hi,
> I have a production server running SQL 2000 SP2 on Windows 2000 server. I
> have to migrate all the databases on this production server to a new
> server
> running SQL Server 2000 SP4 on Windows 2003 Server.
> Are there any known issues? How should I proceed ? Apply SP4 on the
> current
> Production Server first and then migrate? Any insight will be greatly
> appreciated. Thanks.
Sunday, March 11, 2012
Apply SP2 after applying CTP?
Should I apply SP2 even though I have already installed the community preview?
Yes, I'd suggest that you apply the released SP2 on top of the CTP. There were several fixes that were included in the released version.
Thanks,
Sam Lester (MSFT)
Thursday, February 9, 2012
Anything new about RS SP2?
Anybody knows when RS SP2 will be available?
Thanks.
VictorQuestion of the month.
http://www.msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=50f4abcf-371b-4675-ba27-4ec9223ed375
Adrian M.
MCP
"Victor" <Victor@.discussions.microsoft.com> wrote in message
news:8DFE38B6-F1F0-4C45-B13F-4142B7038C58@.microsoft.com...
> Anybody knows when RS SP2 will be available?
> Thanks.
> Victor
>|||Thank you.
Looks like we are waiting it as a bride waits a wedding.
Victor
"Adrian M." wrote:
> Question of the month.
> http://www.msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=50f4abcf-371b-4675-ba27-4ec9223ed375
>
> --
> Adrian M.
> MCP
>
> "Victor" <Victor@.discussions.microsoft.com> wrote in message
> news:8DFE38B6-F1F0-4C45-B13F-4142B7038C58@.microsoft.com...
> > Anybody knows when RS SP2 will be available?
> >
> > Thanks.
> > Victor
> >
>
>
Thanks.
VictorQuestion of the month.
http://www.msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=50f4abcf-371b-4675-ba27-4ec9223ed375
Adrian M.
MCP
"Victor" <Victor@.discussions.microsoft.com> wrote in message
news:8DFE38B6-F1F0-4C45-B13F-4142B7038C58@.microsoft.com...
> Anybody knows when RS SP2 will be available?
> Thanks.
> Victor
>|||Thank you.
Looks like we are waiting it as a bride waits a wedding.
Victor
"Adrian M." wrote:
> Question of the month.
> http://www.msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=50f4abcf-371b-4675-ba27-4ec9223ed375
>
> --
> Adrian M.
> MCP
>
> "Victor" <Victor@.discussions.microsoft.com> wrote in message
> news:8DFE38B6-F1F0-4C45-B13F-4142B7038C58@.microsoft.com...
> > Anybody knows when RS SP2 will be available?
> >
> > Thanks.
> > Victor
> >
>
>
Anyone using SQL2005 Build 3175?
Hi,
Is post SP2 hotfix build 3175 a good build to use?
Thanks
ChrisYes, we have deployed it to production 4 weeks ago and it's been about as
stable as any other post-SP2 fix. :-)
--
Aaron Bertrand
SQL Server MVP
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
> Hi,
> Is post SP2 hotfix build 3175 a good build to use?
> Thanks
> Chris
>|||That's good to hear Aaron. We use sp_OA but are finding it difficult to test
if we actually have the memory leak problem that build 3175 fixes.
Chris
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:emuv4g40HHA.5160@.TK2MSFTNGP05.phx.gbl...
> Yes, we have deployed it to production 4 weeks ago and it's been about as
> stable as any other post-SP2 fix. :-)
> --
> Aaron Bertrand
> SQL Server MVP
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> Is post SP2 hotfix build 3175 a good build to use?
>> Thanks
>> Chris
>
Is post SP2 hotfix build 3175 a good build to use?
Thanks
ChrisYes, we have deployed it to production 4 weeks ago and it's been about as
stable as any other post-SP2 fix. :-)
--
Aaron Bertrand
SQL Server MVP
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
> Hi,
> Is post SP2 hotfix build 3175 a good build to use?
> Thanks
> Chris
>|||That's good to hear Aaron. We use sp_OA but are finding it difficult to test
if we actually have the memory leak problem that build 3175 fixes.
Chris
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:emuv4g40HHA.5160@.TK2MSFTNGP05.phx.gbl...
> Yes, we have deployed it to production 4 weeks ago and it's been about as
> stable as any other post-SP2 fix. :-)
> --
> Aaron Bertrand
> SQL Server MVP
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> Is post SP2 hotfix build 3175 a good build to use?
>> Thanks
>> Chris
>
Anyone using SQL2005 Build 3175?
Hi,
Is post SP2 hotfix build 3175 a good build to use?
Thanks
ChrisYes, we have deployed it to production 4 weeks ago and it's been about as
stable as any other post-SP2 fix. :-)
Aaron Bertrand
SQL Server MVP
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
> Hi,
> Is post SP2 hotfix build 3175 a good build to use?
> Thanks
> Chris
>|||That's good to hear Aaron. We use sp_OA but are finding it difficult to test
if we actually have the memory leak problem that build 3175 fixes.
Chris
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:emuv4g40HHA.5160@.TK2MSFTNGP05.phx.gbl...
> Yes, we have deployed it to production 4 weeks ago and it's been about as
> stable as any other post-SP2 fix. :-)
> --
> Aaron Bertrand
> SQL Server MVP
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
>
Is post SP2 hotfix build 3175 a good build to use?
Thanks
ChrisYes, we have deployed it to production 4 weeks ago and it's been about as
stable as any other post-SP2 fix. :-)
Aaron Bertrand
SQL Server MVP
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
> Hi,
> Is post SP2 hotfix build 3175 a good build to use?
> Thanks
> Chris
>|||That's good to hear Aaron. We use sp_OA but are finding it difficult to test
if we actually have the memory leak problem that build 3175 fixes.
Chris
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:emuv4g40HHA.5160@.TK2MSFTNGP05.phx.gbl...
> Yes, we have deployed it to production 4 weeks ago and it's been about as
> stable as any other post-SP2 fix. :-)
> --
> Aaron Bertrand
> SQL Server MVP
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:OzWk0V40HHA.4824@.TK2MSFTNGP02.phx.gbl...
>
Subscribe to:
Posts (Atom)