sql server tools: windows

Showing posts with label windows. Show all posts

Sunday, March 25, 2012

Architecture question.

Hi
I have a Windows Form running in 40 clients around the city, those apps are
communicating with a central SQLDB hosted in a hosting company (each one is
sending data, waiting for data comparisons and receiving the data back). I
have been using a Web Service to make the link between my apps and the SQLDB
,
but now I want to connect my Windows Form apps directly to de SQLServer
(because I think the roundtrip is going to be faster, which is the most
important factor in my app)
My question to the architects and everyone:
Is this a good, secure, recommended, intelligent practice or this is a big
big mistake '
thks
kengood - Prototype it and see. Depends on the specific case usage and
implementation. You may find that the old style tightly coupled connection
is faster.
secure - Unencrypted xml is easier to intercept and read than unencrypted
native sql network calls. Using an encrypted protocol, it makes little
difference between the two.
recommended, intelligent practice or this is a big big mistake - Consider
the above and decide based on your requirement priorities.
"Kenny M." <KennyM@.discussions.microsoft.com> wrote in message
news:72C3EF9C-7DF4-4C85-A43B-8CE0C5E63388@.microsoft.com...
> Hi
> I have a Windows Form running in 40 clients around the city, those apps
are
> communicating with a central SQLDB hosted in a hosting company (each one
is
> sending data, waiting for data comparisons and receiving the data back). I
> have been using a Web Service to make the link between my apps and the
SQLDB,
> but now I want to connect my Windows Form apps directly to de SQLServer
> (because I think the roundtrip is going to be faster, which is the most
> important factor in my app)
> My question to the architects and everyone:
> Is this a good, secure, recommended, intelligent practice or this is a big
> big mistake '
>
> thks
> ken

Thursday, March 22, 2012

APPS for SSIS

Help!
Does anyone know where can i find some windows or web applications using ssis for manipulations?

Are you looking for case studies? Or actual applications (executables) that incorporate SSIS?|||Hi,
an actual application (code sample) that use or manipulate ssis, hope you can help me on this one

Thanks|||

arsonist wrote:
Hi,
an actual application (code sample) that use or manipulate ssis, hope you can help me on this one
Thanks

This link should help: http://msdn2.microsoft.com/en-us/library/ms345167.aspx

Apps cannot connect to SQL after server upgrade to 2003 R2

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.
>

Tuesday, March 20, 2012

Applying SSIS in Application

Is there anyway I can integrate the ssis in Web applications or Windows applications?

Thanks

Yes. There are API's available that allow you to execute packages programatically and also to consume data from them (which is a very cool feature). These APIs allow the sort of integration that you're probably after.

This is a good place to start:

Integration Services Developer InfoCenter
(http://msdn2.microsoft.com/en-us/library/ms137709.aspx)

-Jamie

Applying SQL hotfixes to a SQL cluster

Gurus,
Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
2003 SP1 is the OS. Are there any special rules I must follow to execute
the SQL hotfix on each node of the cluster? I am assuming I just need to
apply the SQL hotfix to each cluster node and that's it. I am hoping it is
that easy.
--
SpinRecent hotfix installers are typically cluster aware. So in general you don't
need to apply the hotfix on each node. Apply the hotfix on the one that owns
the SQL instance, and the installer will apply the fix to the other nodes for
you.
But read the documentation for your particular hotfix to make sure that is
indeed the case.
Linchi
"Spin" wrote:
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it is
> that easy.
> --
> Spin
>
>|||Make sure Windows Task Schedular is running on both machines, the setup uses
it to apply the hotfix to the other node.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Spin" <Spin@.spin.com> wrote in message
news:4ifir0F3grg8U1@.individual.net...
> Gurus,
> Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> 2003 SP1 is the OS. Are there any special rules I must follow to execute
> the SQL hotfix on each node of the cluster? I am assuming I just need to
> apply the SQL hotfix to each cluster node and that's it. I am hoping it
> is that easy.
> --
> Spin
>|||Hi gurus,
I have a problem. For security purposes I work with two databases; I
use one as production DB (pdb) and the other (cdb) serves as a secure
copy of the production database; and I want to regularly update the
secure copy with the work that I do in the production databasse i.e.
update exsiting stored procedures, tables, views and diagrams or copy
new ones into the secure copy.
A program that at the end of each session in the production db asks if
I want to update the secure copy.
Anyone has an idea for a begginner?
Thanks
Yao
Tony Rogerson wrote:
> Make sure Windows Task Schedular is running on both machines, the setup uses
> it to apply the hotfix to the other node.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
> Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Spin" <Spin@.spin.com> wrote in message
> news:4ifir0F3grg8U1@.individual.net...
> > Gurus,
> >
> > Running two instances of SQL on a SQL Server 2000 cluster. Windows Server
> > 2003 SP1 is the OS. Are there any special rules I must follow to execute
> > the SQL hotfix on each node of the cluster? I am assuming I just need to
> > apply the SQL hotfix to each cluster node and that's it. I am hoping it
> > is that easy.
> >
> > --
> > Spin
> >
> >sql

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

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

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

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon Shargorodsky
Leon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com
|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard tha
t
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
--
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> > I'm getting this error message while trying to apply SP3a to SQL
> > Server 2000 Standard that runs on Windows Server 2003:
> >
> > "Setup was unable to verify the state of the server for an upgrade.
> > Verify the server is able to start and that you provided a valid sa
> > password and restart setup"
> >
> > My sa password is definitely valid (verified), I'm able to stop and
> > restart SQL Server service manually with no problem. Please advise,
> > this problem happens every time I try to run SP3 or SP3a for SQL
> > Server 2000 Standard that runs on Windows Server 2003.
> >
> > Thanks you in advance for your help,
> >
> > Leon Shargorodsky
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

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,

the end of that file has the following information:

I basically got very, very similar symptons to what I expereienced when installing SP2.

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.

So does this mean that the logs are not correct and SP2 and the updates have been successfully applied?

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.

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.

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.

Sunday, March 11, 2012

Apply this internet package for Microsoft Windows

--bjszjhemnhj
Content-Type: multipart/related; boundary="vqzkxajtgdbsybf";
type="multipart/alternative"
--vqzkxajtgdbsybf
Content-Type: multipart/alternative; boundary="cszcjnmsnamlbgbt"
--cszcjnmsnamlbgbt
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Microsoft Customer
this is the latest version of security update, the
"October 2003, Cumulative Patch" update which resolves
all known security vulnerabilities affecting
MS Internet Explorer, MS Outlook and MS Outlook Express
as well as three new vulnerabilities.
Install now to help protect your computer
from these vulnerabilities, the most serious of which could
allow an malicious user to run code on your system.
This update includes the functionality = of all previously released patches.
System requirements: Windows 95/98/Me/2000/NT/XP
This update applies to:
- MS Internet Explorer, version 4.01 and later
- MS Outlook, version 8.00 and later
- MS Outlook Express, version 4.01 and later
Recommendation: Customers should install the patch = at the earliest opportunity.
How to install: Run attached file. Choose Yes on displayed dialog box.
How to use: You don't need to do anything after installing this item.
Microsoft Product Support Services and Knowledge Base articles = can be found on the Microsoft Technical Support web site.
http://support.microsoft.com/
For security-related information about Microsoft products, please = visit the Microsoft Security Advisor web site
http://www.microsoft.com/security/
Thank you for using Microsoft products.
Please do not reply to this message.
It was sent from an unmonitored e-mail address and we are unable = to respond to any replies.
---
The names of the actual companies and products mentioned = herein are the trademarks of their respective owners.
Copyright 2003 Microsoft Corporation.
--cszcjnmsnamlbgbt
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
&
.navtext{color:#ffffff;text-decoration:none}
Microsoft
All Products |
Support |
Search |
Microsoft.com Guide
Microsoft Home
Microsoft Customer
this is the latest version of security update, the
"October 2003, Cumulative Patch" update which resolves
all known security vulnerabilities affecting
MS Internet Explorer, MS Outlook and MS Outlook Express
as well as three new vulnerabilities.
Install now to help protect your computer
from these vulnerabilities, the most serious of which could
allow an malicious user to run code on your system.
This update includes the functionality = of all previously released patches.
System requirements
Windows 95/98/Me/2000/NT/XP
This update applies to
MS Internet Explorer, version 4.01 and later
MS Outlook, version 8.00 and later
MS Outlook Express, version 4.01 and later
Recommendation
Customers should install the patch = at the earliest opportunity.
How to install
Run attached file. = Choose Yes on displayed dialog box.
How to use
You don't need to do = anything after installing this item.
Microsoft Product Support Services and Knowledge Base articles
can be found on the Microsoft Technical Support web site. = For security-related information about Microsoft products, please = visit the
Microsoft Security Advisor web site, = or Contact Us.
Thank you for using Microsoft products.
Please do not reply to this message. = It was sent from an unmonitored e-mail address and we are unable = to respond to any replies.
The names of the actual companies and = products mentioned herein are the trademarks = of their respective owners.
Contact Us
|
Legal
|
TRUSTe
©2003 Microsoft Corporation. All rights reserved.
Terms of Use
|
Privacy Statement |
Accessibility

--cszcjnmsnamlbgbt--
--vqzkxajtgdbsybf
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-ID: <aldcmwj>
R0lGODlhaAA7APcAAP///+rp6puSp6GZrDUjUUc6Zn53mFJMdbGvvVtXh2xre8bF1x8cU4yLprOy
zIGArlZWu25ux319xWpqnnNzppaWy46OvKKizZqavLa2176+283N5sfH34uLmpKSoNvb7c7O3L29
yqOjrtTU4crK1Nvb5erq9O/v+O7u99PT2sbGzePj6vLy99jY3Pv7/vb2+fn5++/v8Kqr0oWHuNbX
55SVoszN28vM2pGUr7S1vqqtv52frOPl8CQvaquz2Ojp7pmn3Ozu83OPzmmT6F1/xo6Voh9p2C5z
3EWC31mS40Zxr4uw6LXN8iZkuXmn55q97PH2/Yir1rbL5iVTh3Oj2cvX5Pv9/+/w8QF8606h62Wk
3n+dubnY9abB2c7n/83h9Nji6weK+CGJ4Vim6WyKpKWssgFyyAaV/0Km8Gyx6HW57FJxicDP2+Tt
9Pj8/wOa/wmL5wqd/w6V8heb91e5+mS9+VmLr4vD6qvc/b/j/Mbn/sTi9rvX6szq/tPt/9ju/dzx
/+n2/+74//P6/+3w8hOh/xOW6yCm/iuu/zWv/0m4/XTH/IXK95TP9qPV9bfi/tDn9tfp9OP0/93r
9L3Izy6Vzj22/lrC/mfG/JvJ5JGntAyd6IbX/3zD6GzP/3jV/2uoxHqbqujv8g6MvJTj/2HF5pXV
606zz6Hp/63v/7j1/8Ps88b8/rbj5RKOkE2wr3OGhoKGhv7///Dx8V2alqvm4Zni1YPRvx5uVwyO
X0q2hLTvw8X10gx2H4PXkkuoV5zkoQeADZu7mmzIVEO7HIXbaGfLMPz8+97d2/Px7v///+bl5eHg
4P7+/v39/fT09PLy8u7u7gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAaAA7AAAI/gCVCRxI
sKDBgwgTKlzIsKHDhxAjKgwiqs2kSJEgQfqyp2PHLxoxTmojSpTEkyglBrGYcU+el3n09PEDSFKg
mzclAfLTRw/MPV4gjTSZsmhRURchuXwUs88fSYIGubEiqyqAq1gBNLPiRlCgPz197tE4MojRswuD
JHX5UiagQILcNMtKl26zu3etuBgUaKcePXv0QIo0iSjaw8raROKYh6nbuFbmVpVlpbKby4Mya858
eWrlrV0l/fECWDBhw4hPimoJUw9NQVa0Yg6kk6dPmD9xt/Xi52kgKG4GCRLtpTjZNmZTQ5yktLXT
QFNDA+qJe2wkkgkrrmWrx4tv0X6M/gvFrnzh6uaO+wCKOhzs7TzWyUesyDom7z9//EAKOh51eYKK
sdWWH1D15cd78J12GFJKufRXcfwNNtR/ANYXE006UfdSfBQq1lxM3fFHWFlojRBCCA5goMMK5y3V
1B879VGdUMlRqIxaG7kUmHEikVTjQyuAcGIGDmSQwQUYzPBAA1UIKJMfUCI4Vhs2EjTJKrWYwogp
mXSxY0iTTLhQAC2ocKIDHGywgAwYWPDAm3AeIIVztr3E1FiFVSnQJLXc4ksxuujyiy6npNGFYBKK
WRAzKZipAgkp8ACCAyLg0MClDcD5ppIUVNCFFDL1oSF8Qvn3nyi8+KIqMH8aQwwx/66EMQcoVQxG
mI/KBEBCCCSo0MIPLJSJwA6YFvsmBlFkYgopUTxwgQ8XXGBBBRUA0QUXeJp6qi2r2rKLLcAU42qs
WIRhR623YpdDNM4wQ0IOInggrwfFNoCDDl20wooqqaSCCil3SHCBBgQXnAGbFmCAgQMkBKDnLsMU
4wswvPCySy3DuLpJGFiY4YodX6RrUhnOIFDDvPNeqkkXfKzCyssv8+svwM5uYPPNONusAZszEEEE
GoooQsfQdRRdxyJII83I0ow04nQjjkTtCB5cVN3KMBEXA8wuFbMC6Cu5jIJFLsG4oonIQeQQQw4o
a5KsI6moogrMMMvt77+kCPzB3v589+03BxdQ0IFyotyCdTFap7I1K7Z4YskmcIwSTC+9KMHGSD6S
0AIJHkRxByekkIJKv3LPXbfMeOddgQmst+466xoAIUEEEUzAQNBD02H00UkvwnTTT0s9ddV4ZPEK
1hH/qTUnlyDyRi659BJMMLiEgrkoQSwTAjMefPIJ6KKPHnfppfeLCt6cCDFDmjT8AMP7MJywwQW0
1187Aco5osUYyGNtjC+ccFwhzuCK6U0OF2uoQht8FAMEoMADnfge+M7Xrwpa8HyhI0X6JGCwDGhg
fvYLoe1wRzSj9c53THsa1KRGNS6oYQxZ0AXyjKGLUlzCEoeIQxjIRjnKTYESC/7EnjJyYAIRRMF7
4Auf+Cp4vtRxghNOiEAHjxTC+k3gfsp5ghPSAIqMBeoUlkjEIeYgBzjwEBdonEIOgmgWSDlgC0h8
YgabSEcncuITUZQBwYxERftRYAIToEDtbie0EhbthL9TofBa6IT9jeEVgQpUJcZoCDEUcHqUw8UU
ysBGZZQgBAvAgSfimMQMmjJ0T/SeGiKgRw3w8QKz+2Mgp/UALKamC1FYwha1AElJzkEMYiDb5HqB
wE2SRIjR0MEIGoCJUUqwlKd84h0/4QlMRKACezQSLAM5A2pR6wF/JGTudofIFAaPhVW7AxWooIX9
ZSELv4hnJYA5CjQScw1rUP/jMQeCgA/gQA2ecOYzpUnQaVKzmtfM5pEkMIFpebMCtZwA/lJTBR88
YQlRcIITQBHPeNrhCEcwQhPQmM8EALEkAwnBDTBAhWYG1HukTCVMD4oJTBDBAgrNAEOnZYE/vomh
4jQk75KWyHNGrYWO0KUT1tlOWnRUCUdQQhOaoIQ12GEKsVCgEAVSAge88RIufelMxxrQal7iEkLg
oCv5uFOffvOPE0XMMvjggy74IAoZ3UI8aYEEJUh1CkoggxIOUIbCbFUZyczADM4K1rI69rHVxARj
kyDFtRppp9OawR8pAFQS6s6EvSuq0xZZNS444gkZ1SgVQkELWvjMr1QlQgT+pgALG+yTIDrgwAPo
wFiwhtWxNZUsYxVBWYX6YAYT0CwgHwDRB0i0PNGoghTsCoQoaEIYQhCCz7ZLhCYoIAdD+ZEyQqAB
C4xBEb09a3Brmt5LBE0RWYiAB/mo2EBSoJvfdG5QP3vI0JpztOgsLR8y8QTU4jUK2U2wEIagBAWU
AQy3JcgIUqSF97b3wu9VhCXQwErLKpYCDvXmmygQV+UEQLpScKUPfACEFjuBCGuAhQ4gXBLxIjZa
QrBEhtGL3rPyOMOWCHIiOkxfCzT0oc2lwH7J6d+lKTLAVfPIdAu8hCUAwQlCIIMBikAJCEeYIMm4
gAxmkIggB3nHOzazJcb+QIXZ6bHIIPZmT0FMYj2RyUw50EEZRIAASnzheoctSJEekIgyq/nQalaE
E2QXAYHlFANx1iyILYDcJYOWqP9d4VFLi62PgEQkGAl1mI5p44HcYMxoQISqC21oIYcxDUuowOwk
IAMOTDEDGAAnBR5gARyAE5Al1pMytIM5UiuEBxWwQBIOoepmO1sRd/BBBWgnMGo9a758xECmcOBr
QE5Av55lMqadbNThldYjX/h0qEVyvVIDiFpEOIS85b3qOjBBBrODgL4foCZoWVsG2cZAt5fL7ToL
WyAVWeAxA42QScjgAkQoRCHmrYhGgDAC+s54AjbAAQ4s4GDeFHOuvf3/ABwMQBgiUHK4L620TJP2
3J7WSEhG1MmJRKILsJzDxBfxhfLWL+MZn4AGOm5rgj2cWrJ8wAB2sAMRFEMYBtcTRUpCdXcbZDV8
sIAExoAHHuA7At2sYv3Q5PEOQmvXTE/7DlCu8kLyd6gtJzeANw3zPaRb5uwOIkoV0gY2SNsCgG+0
DFJwJFhWMbkDK7qHRcD4xjMeBxMoQAGEHYSpWz0hPlhANHxggWtyYBnMQAYIKvBwCZj+9GCHqAUc
kFMdOF4EOzBAAXoA2JX3d9zAm7u5oxxzW4164doaiAM0rwwU0IAHz4hGAEDfAjH74PTQn4G0EpAA
Z9HX9Y03wAEKcIAB/oDAYQc/CQkcEIBoPAMGzoDBM2KwfGa0QAMXOBLg5y8B6V/gAVNowhQogIEV
61kEDXAAPdADTVAJaKBjtgd3KCR3mrZ7nWZ36kZzx0QIV5AQGNAC5Xd+x6B+7Md8KYBN0oZkziIt
E4AAKTAACtBQ8ZIA3NcBKrAMMRB+RfEAzLAM0aAMz/ACLwANyrcMyNACKXABCwA40VKEFPBwRtYE
cjAHhmAEU5AAAzgFYjAHrHZmCVhODPhyvAeBtkJzNUYIs5AQNLgM5VeBV9CDoQeEIZABICADbviG
FBAtRqYAzCAQAVACOSAACFACMngYFqACNRgAgiiIy+CDLQCEJCAD/yWgAV7ViHF4ATOQAFMABxI3
cWM0B6tWhQjoduIWd7nXgC20hXfHbkOBPRSYECFgAchQg4VYiMyQhikAAjdwAStgAydyIm1yARVA
AQXQASvQhzYSAA2AAav4iq/4g0AYiyRwATRQAiqgAggwAxYgA7t4AAcQAjcIjBTSAgYwAySADOB4
iMkoi7uCAQuQJBYgZj3FfQOwDNpYJSnQAROAAZozjuS4AAsAfzLgAGzyACzYfXX4jlVSAmVAfQ+w
MCRgAyRAAvhIMCmCXNtXAAYQAu4okHryAzaAARNgjQYJJxNAfRF5AAaQAy2QjRYpdWBQBV2QawrA
gpLHfQpgAA1ggiMrYJInKWxIsRhfUAU82ZMj0Iwr8AM3qY3E9ntVV3lDWSUBAQA7
--vqzkxajtgdbsybf
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-ID: <rrkyatz>
R0lGODlhDAAMANUAAP////f3//f39+/v9+/v797m987W787W5sXW5rXF76295qW975y175St75St
3pSlzoyl1oSl5oylzoycxXOU3nOMxWOM5mOM3mOE1lqE3mOEvVKE1lp7xVJ71lJ7zlJ7xVJ7vUp7
zkpzzkpzxVJzrUprvUJrxUJrvUJjtTpjtTpjrTparTpapQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAADAAMAAAIjAABAAhwwMGFCxAQ
CACwkICDDBYSLGjQwQEBhg8zDBAIYIEIBwIQdLjAoOOFgSFMIICwIUMEAxQwCBxhAgKHDh5C6DQA
IIGJEyA4fPAwYoQCAAVKoEgBQsKJEidQ8CyRYumDA1VTqNBQQYXXFQofsPB6AIAKFiweNBTLoiza
BxcFCjgwgQSJCQcWCggIADs=
--vqzkxajtgdbsybf--
--bjszjhemnhj
Content-Type: application/x-compressed; name="Q253716.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment
--bjszjhemnhj--This is a multi-part message in MIME format.
--=_NextPart_000_0253_01C3898B.E23B6A70
Content-Type: multipart/alternative;
boundary="--=_NextPart_001_0254_01C3898B.E23B6A70"
--=_NextPart_001_0254_01C3898B.E23B6A70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
VIRUS ALERT!!!!
-- Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=3Ddjq&as =ugroup=3Dmicrosoft.public.sqlserver
"Sixdollarclassifieds" <bqgvzyx@.gtqk.com> wrote in message =news:%23uSjWvNiDHA.1956@.TK2MSFTNGP10.phx.gbl...
Microsoft All Products | Support | Search | =Microsoft.com Guide Microsoft Home
Microsoft Customer
this is the latest version of security update, the "October =2003, Cumulative Patch" update which resolves all known security =vulnerabilities affecting MS Internet Explorer, MS Outlook and MS =Outlook Express as well as three new vulnerabilities. Install now to =help protect your computer from these vulnerabilities, the most serious =of which could allow an malicious user to run code on your system. This =update includes the functionality of all previously released patches.
System requirements Windows 95/98/Me/2000/NT/XP This update applies to MS Internet Explorer, version 4.01 and =later
MS Outlook, version 8.00 and later
MS Outlook Express, version 4.01 and later Recommendation Customers should install the patch at the =earliest opportunity. How to install Run attached file. Choose Yes on displayed =dialog box. How to use You don't need to do anything after installing this =item.
Microsoft Product Support Services and Knowledge Base articles =can be found on the Microsoft Technical Support web site. For =security-related information about Microsoft products, please visit the =Microsoft Security Advisor web site, or Contact Us.
Thank you for using Microsoft products.
Please do not reply to this message. It was sent from an =unmonitored e-mail address and we are unable to respond to any replies.
---
The names of the actual companies and products mentioned herein =are the trademarks of their respective owners.
Contact Us | Legal | TRUSTe =A92003 Microsoft Corporation. All rights reserved. Terms of Use =| Privacy Statement | Accessibility --=_NextPart_001_0254_01C3898B.E23B6A70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

.navtext {
COLOR: #ffffff; TEXT-DECORATION: none
}
VIRUS ALERT!!!!
-- Tibor Karaszi, SQL Server MVPArchive at: http://groups.google.com/groups?oi=3Ddjq&as">http://groups.go=ogle.com/groups?oi=3Ddjq&as ugroup=3Dmicrosoft.public.sqlserver
"Sixdollarclassifieds" wrote in =message news:%23uSjWvNiDHA.=1956@.TK2MSFTNGP10.phx.gbl...
Microsoft
All Products | Support | Search | Microsoft.com Guide
Microsoft Home
Microsoft Customerthis is the latest =version of security update, the "October 2003, Cumulative Patch" update =which resolves all known security vulnerabilities affecting MS =Internet Explorer, MS Outlook and MS Outlook Express as well as three new = vulnerabilities. Install now to help protect your computer from =these vulnerabilities, the most serious of which could allow an =malicious user to run code on your system. This update includes the =functionality of all previously released patches. =
System requirements
Windows =95/98/Me/2000/NT/XP
This update applies to
MS Internet Explorer, version 4.01 and laterMS Outlook, version 8.00 and laterMS Outlook =Express, version 4.01 and later
Recommendation
Customers should install the patch at =the earliest opportunity.
How to install
Run attached file. Choose Yes on =displayed dialog box.
How to use
You don't need to do anything after =installing this item.
Microsoft Product Support Services and =Knowledge Base articles can be found on the Microsoft Technical Support web site. For security-related information about Microsoft products, please =visit the Microsoft Security Advisor web site, or Contact Us. Thank you for using =Microsoft products.Please do not reply to =this message. It was sent from an unmonitored e-mail address and we =are unable to respond to any replies.
The names of the actual companies =and products mentioned herein are the trademarks of their respective =owners.
Contact Us | Legal = | TRUSTe
=A92003 Microsoft Corporation. =All rights reserved. Terms of Use | Privacy Statement | Accessibility =

--=_NextPart_001_0254_01C3898B.E23B6A70--
--=_NextPart_000_0253_01C3898B.E23B6A70
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-ID: <024601c3897b$1ea66570$216411ac@.tibork>
R0lGODlhaAA7APcAAP///+rp6puSp6GZrDUjUUc6Zn53mFJMdbGvvVtXh2xre8bF1x8cU4yLprOy
zIGArlZWu25ux319xWpqnnNzppaWy46OvKKizZqavLa2176+283N5sfH34uLmpKSoNvb7c7O3L29
yqOjrtTU4crK1Nvb5erq9O/v+O7u99PT2sbGzePj6vLy99jY3Pv7/vb2+fn5++/v8Kqr0oWHuNbX
55SVoszN28vM2pGUr7S1vqqtv52frOPl8CQvaquz2Ojp7pmn3Ozu83OPzmmT6F1/xo6Voh9p2C5z
3EWC31mS40Zxr4uw6LXN8iZkuXmn55q97PH2/Yir1rbL5iVTh3Oj2cvX5Pv9/+/w8QF8606h62Wk
3n+dubnY9abB2c7n/83h9Nji6weK+CGJ4Vim6WyKpKWssgFyyAaV/0Km8Gyx6HW57FJxicDP2+Tt
9Pj8/wOa/wmL5wqd/w6V8heb91e5+mS9+VmLr4vD6qvc/b/j/Mbn/sTi9rvX6szq/tPt/9ju/dzx
/+n2/+74//P6/+3w8hOh/xOW6yCm/iuu/zWv/0m4/XTH/IXK95TP9qPV9bfi/tDn9tfp9OP0/93r
9L3Izy6Vzj22/lrC/mfG/JvJ5JGntAyd6IbX/3zD6GzP/3jV/2uoxHqbqujv8g6MvJTj/2HF5pXV
606zz6Hp/63v/7j1/8Ps88b8/rbj5RKOkE2wr3OGhoKGhv7///Dx8V2alqvm4Zni1YPRvx5uVwyO
X0q2hLTvw8X10gx2H4PXkkuoV5zkoQeADZu7mmzIVEO7HIXbaGfLMPz8+97d2/Px7v///+bl5eHg
4P7+/v39/fT09PLy8u7u7gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAaAA7AAAI/gCVCRxI
sKDBgwgTKlzIsKHDhxAjKgwiqs2kSJEgQfqyp2PHLxoxTmojSpTEkyglBrGYcU+el3n09PEDSFKg
mzclAfLTRw/MPV4gjTSZsmhRURchuXwUs88fSYIGubEiqyqAq1gBNLPiRlCgPz197tE4MojRswuD
JHX5UiagQILcNMtKl26zu3etuBgUaKcePXv0QIo0iSjaw8raROKYh6nbuFbmVpVlpbKby4Mya858
eWrlrV0l/fECWDBhw4hPimoJUw9NQVa0Yg6kk6dPmD9xt/Xi52kgKG4GCRLtpTjZNmZTQ5yktLXT
QFNDA+qJe2wkkgkrrmWrx4tv0X6M/gvFrnzh6uaO+wCKOhzs7TzWyUesyDom7z9//EAKOh51eYKK
sdWWH1D15cd78J12GFJKufRXcfwNNtR/ANYXE006UfdSfBQq1lxM3fFHWFlojRBCCA5goMMK5y3V
1B879VGdUMlRqIxaG7kUmHEikVTjQyuAcGIGDmSQwQUYzPBAA1UIKJMfUCI4Vhs2EjTJKrWYwogp
mXSxY0iTTLhQAC2ocKIDHGywgAwYWPDAm3AeIIVztr3E1FiFVSnQJLXc4ksxuujyiy6npNGFYBKK
WRAzKZipAgkp8ACCAyLg0MClDcD5ppIUVNCFFDL1oSF8Qvn3nyi8+KIqMH8aQwwx/66EMQcoVQxG
mI/KBEBCCCSo0MIPLJSJwA6YFvsmBlFkYgopUTxwgQ8XXGBBBRUA0QUXeJp6qi2r2rKLLcAU42qs
WIRhR623YpdDNM4wQ0IOInggrwfFNoCDDl20wooqqaSCCil3SHCBBgQXnAGbFmCAgQMkBKDnLsMU
4wswvPCySy3DuLpJGFiY4YodX6RrUhnOIFDDvPNeqkkXfKzCyssv8+svwM5uYPPNONusAZszEEEE
GoooQsfQdRRdxyJII83I0ow04nQjjkTtCB5cVN3KMBEXA8wuFbMC6Cu5jIJFLsG4oonIQeQQQw4o
a5KsI6moogrMMMvt77+kCPzB3v589+03BxdQ0IFyotyCdTFap7I1K7Z4YskmcIwSTC+9KMHGSD6S
0AIJHkRxByekkIJKv3LPXbfMeOddgQmst+466xoAIUEEEUzAQNBD02H00UkvwnTTT0s9ddV4ZPEK
1hH/qTUnlyDyRi659BJMMLiEgrkoQSwTAjMefPIJ6KKPHnfppfeLCt6cCDFDmjT8AMP7MJywwQW0
1187Aco5osUYyGNtjC+ccFwhzuCK6U0OF2uoQht8FAMEoMADnfge+M7Xrwpa8HyhI0X6JGCwDGhg
fvYLoe1wRzSj9c53THsa1KRGNS6oYQxZ0AXyjKGLUlzCEoeIQxjIRjnKTYESC/7EnjJyYAIRRMF7
4Auf+Cp4vtRxghNOiEAHjxTC+k3gfsp5ghPSAIqMBeoUlkjEIeYgBzjwEBdonEIOgmgWSDlgC0h8
YgabSEcncuITUZQBwYxERftRYAIToEDtbie0EhbthL9TofBa6IT9jeEVgQpUJcZoCDEUcHqUw8UU
ysBGZZQgBAvAgSfimMQMmjJ0T/SeGiKgRw3w8QKz+2Mgp/UALKamC1FYwha1AElJzkEMYiDb5HqB
wE2SRIjR0MEIGoCJUUqwlKd84h0/4QlMRKACezQSLAM5A2pR6wF/JGTudofIFAaPhVW7AxWooIX9
ZSELv4hnJYA5CjQScw1rUP/jMQeCgA/gQA2ecOYzpUnQaVKzmtfM5pEkMIFpebMCtZwA/lJTBR88
YQlRcIITQBHPeNrhCEcwQhPQmM8EALEkAwnBDTBAhWYG1HukTCVMD4oJTBDBAgrNAEOnZYE/vomh
4jQk75KWyHNGrYWO0KUT1tlOWnRUCUdQQhOaoIQ12GEKsVCgEAVSAge88RIufelMxxrQal7iEkLg
oCv5uFOffvOPE0XMMvjggy74IAoZ3UI8aYEEJUh1CkoggxIOUIbCbFUZyczADM4K1rI69rHVxARj
kyDFtRppp9OawR8pAFQS6s6EvSuq0xZZNS444gkZ1SgVQkELWvjMr1QlQgT+pgALG+yTIDrgwAPo
wFiwhtWxNZUsYxVBWYX6YAYT0CwgHwDRB0i0PNGoghTsCoQoaEIYQhCCz7ZLhCYoIAdD+ZEyQqAB
C4xBEb09a3Brmt5LBE0RWYiAB/mo2EBSoJvfdG5QP3vI0JpztOgsLR8y8QTU4jUK2U2wEIagBAWU
AQy3JcgIUqSF97b3wu9VhCXQwErLKpYCDvXmmygQV+UEQLpScKUPfACEFjuBCGuAhQ4gXBLxIjZa
QrBEhtGL3rPyOMOWCHIiOkxfCzT0oc2lwH7J6d+lKTLAVfPIdAu8hCUAwQlCIIMBikAJCEeYIMm4
gAxmkIggB3nHOzazJcb+QIXZ6bHIIPZmT0FMYj2RyUw50EEZRIAASnzheoctSJEekIgyq/nQalaE
E2QXAYHlFANx1iyILYDcJYOWqP9d4VFLi62PgEQkGAl1mI5p44HcYMxoQISqC21oIYcxDUuowOwk
IAMOTDEDGAAnBR5gARyAE5Al1pMytIM5UiuEBxWwQBIOoepmO1sRd/BBBWgnMGo9a758xECmcOBr
QE5Av55lMqadbNThldYjX/h0qEVyvVIDiFpEOIS85b3qOjBBBrODgL4foCZoWVsG2cZAt5fL7ToL
WyAVWeAxA42QScjgAkQoRCHmrYhGgDAC+s54AjbAAQ4s4GDeFHOuvf3/ABwMQBgiUHK4L620TJP2
3J7WSEhG1MmJRKILsJzDxBfxhfLWL+MZn4AGOm5rgj2cWrJ8wAB2sAMRFEMYBtcTRUpCdXcbZDV8
sIAExoAHHuA7At2sYv3Q5PEOQmvXTE/7DlCu8kLyd6gtJzeANw3zPaRb5uwOIkoV0gY2SNsCgG+0
DFJwJFhWMbkDK7qHRcD4xjMeBxMoQAGEHYSpWz0hPlhANHxggWtyYBnMQAYIKvBwCZj+9GCHqAUc
kFMdOF4EOzBAAXoA2JX3d9zAm7u5oxxzW4164doaiAM0rwwU0IAHz4hGAEDfAjH74PTQn4G0EpAA
Z9HX9Y03wAEKcIAB/oDAYQc/CQkcEIBoPAMGzoDBM2KwfGa0QAMXOBLg5y8B6V/gAVNowhQogIEV
61kEDXAAPdADTVAJaKBjtgd3KCR3mrZ7nWZ36kZzx0QIV5AQGNAC5Xd+x6B+7Md8KYBN0oZkziIt
E4AAKTAACtBQ8ZIA3NcBKrAMMRB+RfEAzLAM0aAMz/ACLwANyrcMyNACKXABCwA40VKEFPBwRtYE
cjAHhmAEU5AAAzgFYjAHrHZmCVhODPhyvAeBtkJzNUYIs5AQNLgM5VeBV9CDoQeEIZABICADbviG
FBAtRqYAzCAQAVACOSAACFACMngYFqACNRgAgiiIy+CDLQCEJCAD/yWgAV7ViHF4ATOQAFMABxI3
cWM0B6tWhQjoduIWd7nXgC20hXfHbkOBPRSYECFgAchQg4VYiMyQhikAAjdwAStgAydyIm1yARVA
AQXQASvQhzYSAA2AAav4iq/4g0AYiyRwATRQAiqgAggwAxYgA7t4AAcQAjcIjBTSAgYwAySADOB4
iMkoi7uCAQuQJBYgZj3FfQOwDNpYJSnQAROAAZozjuS4AAsAfzLgAGzyACzYfXX4jlVSAmVAfQ+w
MCRgAyRAAvhIMCmCXNtXAAYQAu4okHryAzaAARNgjQYJJxNAfRF5AAaQAy2QjRYpdWBQBV2QawrA
gpLHfQpgAA1ggiMrYJInKWxIsRhfUAU82ZMj0Iwr8AM3qY3E9ntVV3lDWSUBAQA7
--=_NextPart_000_0253_01C3898B.E23B6A70
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-ID: <024801c3897b$1ea66570$216411ac@.tibork>
R0lGODlhDAAMANUAAP////f3//f39+/v9+/v797m987W787W5sXW5rXF76295qW975y175St75St
3pSlzoyl1oSl5oylzoycxXOU3nOMxWOM5mOM3mOE1lqE3mOEvVKE1lp7xVJ71lJ7zlJ7xVJ7vUp7
zkpzzkpzxVJzrUprvUJrxUJrvUJjtTpjtTpjrTparTpapQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAADAAMAAAIjAABAAhwwMGFCxAQ
CACwkICDDBYSLGjQwQEBhg8zDBAIYIEIBwIQdLjAoOOFgSFMIICwIUMEAxQwCBxhAgKHDh5C6DQA
IIGJEyA4fPAwYoQCAAVKoEgBQsKJEidQ8CyRYumDA1VTqNBQQYXXFQofsPB6AIAKFiweNBTLoiza
BxcFCjgwgQSJCQcWCggIADs=--=_NextPart_000_0253_01C3898B.E23B6A70--

Thursday, March 8, 2012

Application v. Error log. Will I miss anything important?

Hi,
Will I miss anything important in MS SQL Server 2000 if I monitor only MS
Windows 2000 application event log and don't monitor SQL Server error log?
What exactly will I miss?
-- Many thanks, OskarA comment to my previous post.
I suppose errors with severity 19 an higher ar logged into Windows
Application log, so I shouldn't miss any of them when they happen. Is that
true? Also if in SQL Server Enterprise Manager I configure a particular
message so that it is logged, I should see it in Application event log too,
right?
-- Thanks again, Oskar.
"Oskar" wrote:
> Hi,
> Will I miss anything important in MS SQL Server 2000 if I monitor only MS
> Windows 2000 application event log and don't monitor SQL Server error log?
> What exactly will I miss?
> -- Many thanks, Oskar
>

Application starts before SQL is running.

Very basic question.
OS Windows XP pro
On bootup, an application that starts automatically in the start-up folder,
starts before SQL server is running
This only happens on slower hardware, It must be a common problem, what's
the usual solution?
Graham.
%Profound_observation%I just have a loop in my app where I have exception handling on logon and re
try...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Graham." <me@.privacy.com> wrote in message news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com.
.
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up folder
,
> starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||Another option is to have a vbscript with a timer to wait 5 mins or so on
boot, THEN fire off the executable for the app.
TheSQLGuru
President
Indicium Resources, Inc.
"Graham." <me@.privacy.com> wrote in message
news:4686ab60$1_3@.mk-nntp-2.news.uk.tiscali.com...
> Very basic question.
> OS Windows XP pro
> On bootup, an application that starts automatically in the start-up
> folder, starts before SQL server is running
> This only happens on slower hardware, It must be a common problem, what's
> the usual solution?
> --
> Graham.
> %Profound_observation%
>|||you can also check on whether the SQL server service is running
before your application starts trying to connect to the SQL server.
Change the Application to wait and try for 4-5 times(or based on the
customer experience) to connect to the MSSQL service.

Sunday, March 25, 2012

Architecture question.

Thursday, March 22, 2012

APPS for SSIS

Apps cannot connect to SQL after server upgrade to 2003 R2

Tuesday, March 20, 2012

Applying SSIS in Application

Applying SQL hotfixes to a SQL cluster

Applying SQL hotfixes to a SQL cluster

Monday, March 19, 2012

Applying SP4

Applying SP4

Applying SP4

Applying SP2a to SQL 2000/Win 2003

Applying SP2a to SQL 2000/Win 2003

Applying SP2a to SQL 2000/Win 2003

Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)

Applying SP2 for SQL 2005 Enterprise Edition (on 64 bit windows)

Applying service packs

Applying service packs

Applying service packs

Sunday, March 11, 2012

Apply this internet package for Microsoft Windows

Thursday, March 8, 2012

Application v. Error log. Will I miss anything important?

Application starts before SQL is running.

sql server tools

Blog Archive

About Me