Migrating from Developer Edition to Standard Edition

Hello,
I have Reporting Sevices Developer Edition running on a Windows XP Pro
workstation. I want to migrate it to Reporting Services/SQL Server Standard
Edition on a Windows 2003 server. Can this be done? Since the edition of RS
changes, and the edition of SQL Server changes, and the hardware changes, I
need to know if this is feasible, or if it would be better to redeploy the
reports to the new server. BOL isn't very helpful in this area, and I don't
have time to learn C# to use the RS utility.
Thanks in advance.Given that it is so easy to redeploy and the fact that everything is
changing, my advice is to install new and then redeploy.
Bruce L-C
"Cable Guy" <Cable Guy@.discussions.microsoft.com> wrote in message
news:DCD83C56-B311-45EB-90A6-1A5F45B5A87B@.microsoft.com...
> Hello,
> I have Reporting Sevices Developer Edition running on a Windows XP Pro
> workstation. I want to migrate it to Reporting Services/SQL Server
Standard
> Edition on a Windows 2003 server. Can this be done? Since the edition of
RS
> changes, and the edition of SQL Server changes, and the hardware changes,
I
> need to know if this is feasible, or if it would be better to redeploy the
> reports to the new server. BOL isn't very helpful in this area, and I
don't
> have time to learn C# to use the RS utility.
> Thanks in advance.|||Others would need to jump in for your answer. I can't really help you with
that.
Bruce L-C
"Cable Guy" <CableGuy@.discussions.microsoft.com> wrote in message
news:40C1D674-60C1-49AB-B8B6-5483EE8BDE2F@.microsoft.com...
> Hi Bruce,
> Thanks for the reply. That is what I was initially persuaded to do, but
> redeploying introduces the possibility of something being overlooked, and
> that is what we want to avoid. Is it possible to use the RS utility to do
> what we need it to do (i.e. copy the logical contents of the database to a
> new database/server/edition) and have it work properly? Do you know of
> any
> good documentation on the RS utility?
> "Bruce Loehle-Conger" wrote:
>> Given that it is so easy to redeploy and the fact that everything is
>> changing, my advice is to install new and then redeploy.
>> Bruce L-C
>> "Cable Guy" <Cable Guy@.discussions.microsoft.com> wrote in message
>> news:DCD83C56-B311-45EB-90A6-1A5F45B5A87B@.microsoft.com...
>> > Hello,
>> >
>> > I have Reporting Sevices Developer Edition running on a Windows XP Pro
>> > workstation. I want to migrate it to Reporting Services/SQL Server
>> Standard
>> > Edition on a Windows 2003 server. Can this be done? Since the edition
>> > of
>> RS
>> > changes, and the edition of SQL Server changes, and the hardware
>> > changes,
>> I
>> > need to know if this is feasible, or if it would be better to redeploy
>> > the
>> > reports to the new server. BOL isn't very helpful in this area, and I
>> don't
>> > have time to learn C# to use the RS utility.
>> >
>> > Thanks in advance.
>>|||Hi Bruce,
Thanks for the reply. That is what I was initially persuaded to do, but
redeploying introduces the possibility of something being overlooked, and
that is what we want to avoid. Is it possible to use the RS utility to do
what we need it to do (i.e. copy the logical contents of the database to a
new database/server/edition) and have it work properly? Do you know of any
good documentation on the RS utility?
"Bruce Loehle-Conger" wrote:
> Given that it is so easy to redeploy and the fact that everything is
> changing, my advice is to install new and then redeploy.
> Bruce L-C
> "Cable Guy" <Cable Guy@.discussions.microsoft.com> wrote in message
> news:DCD83C56-B311-45EB-90A6-1A5F45B5A87B@.microsoft.com...
> > Hello,
> >
> > I have Reporting Sevices Developer Edition running on a Windows XP Pro
> > workstation. I want to migrate it to Reporting Services/SQL Server
> Standard
> > Edition on a Windows 2003 server. Can this be done? Since the edition of
> RS
> > changes, and the edition of SQL Server changes, and the hardware changes,
> I
> > need to know if this is feasible, or if it would be better to redeploy the
> > reports to the new server. BOL isn't very helpful in this area, and I
> don't
> > have time to learn C# to use the RS utility.
> >
> > Thanks in advance.
>
>sql

MIgrating DTS packages from one machine to another

I am building a new machine (SQL server 2000 SP3a on Windows 2003 R2) for an
exisitng production michine (SQL server 2000 SP3a on Windows 2000) with 27
user databases. I can move databases, logins, scheduled jobs. I have lot of
DTS packages and Maintenance Plans. Is there an easy way to recreate these
DTS packages and Maintenance plans on the new server with out creating each
one of them manually?
--
RKYou can open the package on one server, using DTS Designer, and then using
[Package], [Save As], save it to a different server.
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:F5FA74AD-DFFC-4C10-AC6D-CED5F8DE6203@.microsoft.com...
>I am building a new machine (SQL server 2000 SP3a on Windows 2003 R2) for
>an
> exisitng production michine (SQL server 2000 SP3a on Windows 2000) with 27
> user databases. I can move databases, logins, scheduled jobs. I have lot
> of
> DTS packages and Maintenance Plans. Is there an easy way to recreate these
> DTS packages and Maintenance plans on the new server with out creating
> each
> one of them manually?
> --
> RK|||Arnie Rowland wrote:[vbcol=seagreen]
> You can open the package on one server, using DTS Designer, and then using
> [Package], [Save As], save it to a different server.
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:F5FA74AD-DFFC-4C10-AC6D-CED5F8DE6203@.microsoft.com...
http://www.sqldts.com/?204
Regards
Amish Shah

MIgrating DTS packages from one machine to another

I am building a new machine (SQL server 2000 SP3a on Windows 2003 R2) for an
exisitng production michine (SQL server 2000 SP3a on Windows 2000) with 27
user databases. I can move databases, logins, scheduled jobs. I have lot of
DTS packages and Maintenance Plans. Is there an easy way to recreate these
DTS packages and Maintenance plans on the new server with out creating each
one of them manually?
--
RKYou can open the package on one server, using DTS Designer, and then using
[Package], [Save As], save it to a different server.
--
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:F5FA74AD-DFFC-4C10-AC6D-CED5F8DE6203@.microsoft.com...
>I am building a new machine (SQL server 2000 SP3a on Windows 2003 R2) for
>an
> exisitng production michine (SQL server 2000 SP3a on Windows 2000) with 27
> user databases. I can move databases, logins, scheduled jobs. I have lot
> of
> DTS packages and Maintenance Plans. Is there an easy way to recreate these
> DTS packages and Maintenance plans on the new server with out creating
> each
> one of them manually?
> --
> RK|||Arnie Rowland wrote:
> You can open the package on one server, using DTS Designer, and then using
> [Package], [Save As], save it to a different server.
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:F5FA74AD-DFFC-4C10-AC6D-CED5F8DE6203@.microsoft.com...
> >I am building a new machine (SQL server 2000 SP3a on Windows 2003 R2) for
> >an
> > exisitng production michine (SQL server 2000 SP3a on Windows 2000) with 27
> > user databases. I can move databases, logins, scheduled jobs. I have lot
> > of
> > DTS packages and Maintenance Plans. Is there an easy way to recreate these
> > DTS packages and Maintenance plans on the new server with out creating
> > each
> > one of them manually?
> > --
> > RK
http://www.sqldts.com/?204
Regards
Amish Shah

Migrating DTS packages and SQL Jobs

Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgnRestoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script
Roles and Permissions
--
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn

Migrating DTS packages and SQL Jobs

Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server
.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgnRestoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/col...se
s.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scr...utions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn

Migrating DTS packages and SQL Jobs

Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgn
Restoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn
sql

Migrating Clusters

Hi All,
We have a 2 node cluster running SQL Server 2000 on Windows 2000 which
needs replacing. The nature of our business is 24 hour operation, so
the downtime to do such needs to be as small as possible.
We have a new cluster ready and waiting in our data centre that is
built on Windows 2003 with SQL Server 2000.
Our issues are:
=B7Configuring all the applications to the new Cluster Name / IP
Address - In the past we have found things hard-coded
=B7Migrate all the data (~100GB) over to the new MSA
=B7Smallest downtime possible
The idea's we have come up with already are:
=B7Frigg DNS to point the old cluster name to the new cluster name and
then migrate all the applications to the new name as time permits.
=B7Rename the new nodes as <NAME>3/4 and add these into the existing
cluster; however the MSA is directly connected to Nodes 1/2.
=B7Remove 1 node from the old cluster, add a new node in, fail-over to
new node, remove 2nd old node, add new node, however I'm thinking
this may not work?
Another consideration is that we use SecurePath on the MSA's so this
could be a PITA.
Does anyone have any other suggestions which we could consider?
Thanks
Well, since you asked.
You could do a minimally disruptive replacement by replacing each node with
one of the new nodes. Uninstall SQL from the "other" node, evict the node,
add the node, run the SQL nstaller to install and configure SQL on the new
node. Wait for maintenance window and do a failover test. Repeat with the
other node.
The other process I use to migrate systems is to run a custom log ship
script (they aren't that hard to write, google will point to some nice free
examples.) to get them ready. Do a final log backup and put the old
databases into norecovery mode. Do a final catch up and go live on the new
system. Patch DNS (hint, use the SRV record type). and go. I can switch
over a typical server with 10-30 databases with less than 10 minutes of
downtime this way.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Steve" <SMaxwell@.NationalExpress.com> wrote in message
news:1160476240.405910.76230@.e3g2000cwe.googlegrou ps.com...
Hi All,
We have a 2 node cluster running SQL Server 2000 on Windows 2000 which
needs replacing. The nature of our business is 24 hour operation, so
the downtime to do such needs to be as small as possible.
We have a new cluster ready and waiting in our data centre that is
built on Windows 2003 with SQL Server 2000.
Our issues are:
Configuring all the applications to the new Cluster Name / IP
Address - In the past we have found things hard-coded
Migrate all the data (~100GB) over to the new MSA
Smallest downtime possible
The idea's we have come up with already are:
Frigg DNS to point the old cluster name to the new cluster name and
then migrate all the applications to the new name as time permits.
Rename the new nodes as <NAME>3/4 and add these into the existing
cluster; however the MSA is directly connected to Nodes 1/2.
Remove 1 node from the old cluster, add a new node in, fail-over to
new node, remove 2nd old node, add new node, however I'm thinking
this may not work?
Another consideration is that we use SecurePath on the MSA's so this
could be a PITA.
Does anyone have any other suggestions which we could consider?
Thanks

migrating 7.0 to 2000

i have computer with windows 2000 an sql 7.0 (computerA)
goal is windows 2003 with sql 2005

I see my choices as is:

A) upgrade win2k to 2k3 then upgrade sql7 on w2k3 to sql2k5 on win2k3.
(i see many potential problems with that)

B) have computerB with clean install of win2k3 and install sql2k5 on it.
if this is the case, what is the best / easiest way to get the database from 7 to 2k5? Database copy wizard? dts? attaching the db?

Anything else I should lookout for ?

thnx,
vextThere might be better answers, but I'd set up the new server with the software that you intend to run on it (Windows 2003, SQL 2005). I'd backup the existing database, and restore that backup onto the new server.

-PatP|||what is the actual difference between using the Database copy wizard and Restoring a backup? and is the datafile still the same structure in 2005? will the restore upgrade if not?|||Theoretically, there shouldn't be a difference between Restoring a Backup and Copying a Database. That leads to all kinds of amusing observations, but I'll behave myself (at least for now). The primary difference is that restoring a backup is logically much more "solid" in that there are far fewer ways for it to go wrong...

The Copy Database Wizard is free to make many assumptions, many of which have a significant impact on performance and operational simplicity. These assumptions should not affect the copy of the quality, but I'm often unpleasantly surprised by them.

Restoring a backup is much less problematic for me. While some things (features, objects, etc) might change due to the difference in software releases (SQL 7 to SQL 2005 is a big jump), at least in my experience there will be far fewer surprises than you'd get via the Copy Database Wizard.

-PatP|||understood.

thnx for the input. I will do a restore when the time comes. thnxsql

Migrate Windows 2000 cluster to Windows 2003

Hi,
I am trying to determine the best method for rebuilding some existing
Windows 2000 clusters to Windows 2003. I have both SQL clusters and
some application clusters.
I do not want to upgrade the OS, but rather rebuild from scratch, one
node at a time, using the existing hardware. Is this possible? I am
having a hard time finding documentation on the best process for this
and want to follow the method which will provide me with the smallest
amount of downtime.
thanks for your help!
http://support.microsoft.com/?kbid=313037 explains how to upgrade, but like
you said, you really want to migrate. You can rebuild one node as a time,
and then rejoin the cluster.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Mel" <Qtip027@.hotmail.com> wrote in message
news:a29a42e2.0411301100.34356ad9@.posting.google.c om...
> Hi,
> I am trying to determine the best method for rebuilding some existing
> Windows 2000 clusters to Windows 2003. I have both SQL clusters and
> some application clusters.
> I do not want to upgrade the OS, but rather rebuild from scratch, one
> node at a time, using the existing hardware. Is this possible? I am
> having a hard time finding documentation on the best process for this
> and want to follow the method which will provide me with the smallest
> amount of downtime.
> thanks for your help!
|||Been there, done that, bought the t-shirt. I prefer a mixed solution.
Upgrade THEN reload the OS. More work but less risk. Biggest thing is to
make absolutely sure you have correct 2003 drivers and software for your
SAN.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mel" <Qtip027@.hotmail.com> wrote in message
news:a29a42e2.0411301100.34356ad9@.posting.google.c om...
> Hi,
> I am trying to determine the best method for rebuilding some existing
> Windows 2000 clusters to Windows 2003. I have both SQL clusters and
> some application clusters.
> I do not want to upgrade the OS, but rather rebuild from scratch, one
> node at a time, using the existing hardware. Is this possible? I am
> having a hard time finding documentation on the best process for this
> and want to follow the method which will provide me with the smallest
> amount of downtime.
> thanks for your help!

Migrate users

Does anyone knows if it's possible to migrate users to another server? I use windows 2000 server and SQL server 2000, Integrated windows sequrity.

I want to use the second server as "Standby" Server. On the first server there are already created many windows-accounts. Do I have to create all theat users again on the other server? and all roles and permissions?You can script the users and permissions by selecting the SCRIPT DATABASE USERS AND DATABASE ROLES and the SCRIPT OBJECT LEVEL PERMISSIONS from the Options Tab in the Scripting dialog boxes from within Enterprise manager.

After the scripts are created, you can edit them to remove everything except the Permission statements.

Now you can execute the script anytime you need to re-create the rolls and permissions.|||can these scripts be run on another machine??|||Any SQL script can be run on any SQL Server. The real question is probably should it be run. There should be no harm, if the script does not drop tables/procedures/views, or delete data. You should review the script to make sure you understand what it is doing.

Migrate SQL Server 2000 to a new server

Hi all
My organisation has SQL Server 2000 running on Windows 2000.
We've just had most of our hardware replaced and SQL Server needs to
be transferred to a better machine running Windows Server 2003.
Are there any tools that could help in doing that? In my
understanding, the databases themselves can simply be backed up and
restored on the new machine. But how can all the existing settings,
users and roles be copied to the new server?
Thanks
Hi Manu,
You may want to take a look at this article. It includes information on how
to move databases, logins and passwords, jobs, DTS packages, etc.
How to move databases between computers that are running SQL Server
http://support.microsoft.com/kb/314546/
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:

> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks
>
|||On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:[vbcol=seagreen]
> Hi Manu,
> You may want to take a look at this article. It includes information on how
> to move databases, logins and passwords, jobs, DTS packages, etc.
> How to move databases between computers that are running SQL Serverhttp://support.microsoft.com/kb/314546/
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
>
Hi Ben
Thanks for the reply.
According to the link, in order to transfer usernames and passwords to
SQL Server running on a different machine, the instance should be
running under a domain account. But that is not the case with our
setup. SQL Server is running under local machine accounts.
Any thoughts?
Thanks
|||Manu,
That is only for the DTS Transfer Logins Tasks. You can still use the method
1 of the section 'A complete resolution to transfer logins and passwords
between different versions of SQL Server' and will get the additional benefit
of transfering the original login SID.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:

> On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
> wrote:
> Hi Ben
> Thanks for the reply.
> According to the link, in order to transfer usernames and passwords to
> SQL Server running on a different machine, the instance should be
> running under a domain account. But that is not the case with our
> setup. SQL Server is running under local machine accounts.
> Any thoughts?
> Thanks
>
|||Manu
http://vyaskn.tripod.com/moving_sql_server.htm
"Manu" <mandeep.sekhon@.gmail.com> wrote in message
news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks
|||On Dec 17, 3:06 am, "Uri Dimant" <u...@.iscar.co.il> wrote:[vbcol=seagreen]
> Manuhttp://vyaskn.tripod.com/moving_sql_server.htm
> "Manu" <mandeep.sek...@.gmail.com> wrote in message
> news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
>
>
Hi Uri
Thanks for the reply.
The link that you sent me requires that SQL Server be running on the
same operating system on both the machines.
In my case, however, the OS is changing too. The new machine runs
Windows Server 2003 while the older one was running Windows 2000.
|||On Dec 14, 6:09 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:[vbcol=seagreen]
> Manu,
> That is only for the DTS Transfer Logins Tasks. You can still use the method
> 1 of the section 'A complete resolution to transfer logins and passwords
> between different versions of SQL Server' and will get the additional benefit
> of transfering the original login SID.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
>
>
>
>
>
>
Hi Ben
That worked beautifully.
As mentioned on the web page, default databases assigned to the logins
are different.
Is there any way to assign the default databases apart from writing a
script using 'sp_defaultdb' for each login?
Regards

Migrate SQL Server 2000 to a new server

Hi all
My organisation has SQL Server 2000 running on Windows 2000.
We've just had most of our hardware replaced and SQL Server needs to
be transferred to a better machine running Windows Server 2003.
Are there any tools that could help in doing that? In my
understanding, the databases themselves can simply be backed up and
restored on the new machine. But how can all the existing settings,
users and roles be copied to the new server?
ThanksHi Manu,
You may want to take a look at this article. It includes information on how
to move databases, logins and passwords, jobs, DTS packages, etc.
How to move databases between computers that are running SQL Server
http://support.microsoft.com/kb/314546/
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:
> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks
>|||On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:
> Hi Manu,
> You may want to take a look at this article. It includes information on how
> to move databases, logins and passwords, jobs, DTS packages, etc.
> How to move databases between computers that are running SQL Serverhttp://support.microsoft.com/kb/314546/
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
> > Hi all
> > My organisation has SQL Server 2000 running on Windows 2000.
> > We've just had most of our hardware replaced and SQL Server needs to
> > be transferred to a better machine running Windows Server 2003.
> > Are there any tools that could help in doing that? In my
> > understanding, the databases themselves can simply be backed up and
> > restored on the new machine. But how can all the existing settings,
> > users and roles be copied to the new server?
> > Thanks
Hi Ben
Thanks for the reply.
According to the link, in order to transfer usernames and passwords to
SQL Server running on a different machine, the instance should be
running under a domain account. But that is not the case with our
setup. SQL Server is running under local machine accounts.
Any thoughts?
Thanks|||Manu,
That is only for the DTS Transfer Logins Tasks. You can still use the method
1 of the section 'A complete resolution to transfer logins and passwords
between different versions of SQL Server' and will get the additional benefit
of transfering the original login SID.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:
> On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
> wrote:
> > Hi Manu,
> >
> > You may want to take a look at this article. It includes information on how
> > to move databases, logins and passwords, jobs, DTS packages, etc.
> >
> > How to move databases between computers that are running SQL Serverhttp://support.microsoft.com/kb/314546/
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> > "Manu" wrote:
> > > Hi all
> >
> > > My organisation has SQL Server 2000 running on Windows 2000.
> > > We've just had most of our hardware replaced and SQL Server needs to
> > > be transferred to a better machine running Windows Server 2003.
> >
> > > Are there any tools that could help in doing that? In my
> > > understanding, the databases themselves can simply be backed up and
> > > restored on the new machine. But how can all the existing settings,
> > > users and roles be copied to the new server?
> >
> > > Thanks
> Hi Ben
> Thanks for the reply.
> According to the link, in order to transfer usernames and passwords to
> SQL Server running on a different machine, the instance should be
> running under a domain account. But that is not the case with our
> setup. SQL Server is running under local machine accounts.
> Any thoughts?
> Thanks
>|||Manu
http://vyaskn.tripod.com/moving_sql_server.htm
"Manu" <mandeep.sekhon@.gmail.com> wrote in message
news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks|||On Dec 17, 3:06 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Manuhttp://vyaskn.tripod.com/moving_sql_server.htm
> "Manu" <mandeep.sek...@.gmail.com> wrote in message
> news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
> > Hi all
> > My organisation has SQL Server 2000 running on Windows 2000.
> > We've just had most of our hardware replaced and SQL Server needs to
> > be transferred to a better machine running Windows Server 2003.
> > Are there any tools that could help in doing that? In my
> > understanding, the databases themselves can simply be backed up and
> > restored on the new machine. But how can all the existing settings,
> > users and roles be copied to the new server?
> > Thanks
Hi Uri
Thanks for the reply.
The link that you sent me requires that SQL Server be running on the
same operating system on both the machines.
In my case, however, the OS is changing too. The new machine runs
Windows Server 2003 while the older one was running Windows 2000.|||On Dec 14, 6:09 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:
> Manu,
> That is only for the DTS Transfer Logins Tasks. You can still use the method
> 1 of the section 'A complete resolution to transfer logins and passwords
> between different versions of SQL Server' and will get the additional benefit
> of transfering the original login SID.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
> > On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
> > wrote:
> > > Hi Manu,
> > > You may want to take a look at this article. It includes information on how
> > > to move databases, logins and passwords, jobs, DTS packages, etc.
> > > How to move databases between computers that are running SQL Serverhttp://support.microsoft.com/kb/314546/
> > > Hope this helps,
> > > Ben Nevarez
> > > Senior Database Administrator
> > > AIG SunAmerica
> > > "Manu" wrote:
> > > > Hi all
> > > > My organisation has SQL Server 2000 running on Windows 2000.
> > > > We've just had most of our hardware replaced and SQL Server needs to
> > > > be transferred to a better machine running Windows Server 2003.
> > > > Are there any tools that could help in doing that? In my
> > > > understanding, the databases themselves can simply be backed up and
> > > > restored on the new machine. But how can all the existing settings,
> > > > users and roles be copied to the new server?
> > > > Thanks
> > Hi Ben
> > Thanks for the reply.
> > According to the link, in order to transfer usernames and passwords to
> > SQL Server running on a different machine, the instance should be
> > running under a domain account. But that is not the case with our
> > setup. SQL Server is running under local machine accounts.
> > Any thoughts?
> > Thanks
Hi Ben
That worked beautifully.
As mentioned on the web page, default databases assigned to the logins
are different.
Is there any way to assign the default databases apart from writing a
script using 'sp_defaultdb' for each login?
Regards

Migrate SQL Server 2000 to a new server

Hi all
My organisation has SQL Server 2000 running on Windows 2000.
We've just had most of our hardware replaced and SQL Server needs to
be transferred to a better machine running Windows Server 2003.
Are there any tools that could help in doing that? In my
understanding, the databases themselves can simply be backed up and
restored on the new machine. But how can all the existing settings,
users and roles be copied to the new server?
ThanksHi Manu,
You may want to take a look at this article. It includes information on how
to move databases, logins and passwords, jobs, DTS packages, etc.
How to move databases between computers that are running SQL Server
http://support.microsoft.com/kb/314546/
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:

> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks
>|||On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:[vbcol=seagreen]
> Hi Manu,
> You may want to take a look at this article. It includes information on ho
w
> to move databases, logins and passwords, jobs, DTS packages, etc.
> How to move databases between computers that are running SQL Serverhttp://
support.microsoft.com/kb/314546/
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
>
>
>
Hi Ben
Thanks for the reply.
According to the link, in order to transfer usernames and passwords to
SQL Server running on a different machine, the instance should be
running under a domain account. But that is not the case with our
setup. SQL Server is running under local machine accounts.
Any thoughts?
Thanks|||Manu,
That is only for the DTS Transfer Logins Tasks. You can still use the method
1 of the section 'A complete resolution to transfer logins and passwords
between different versions of SQL Server' and will get the additional benefi
t
of transfering the original login SID.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:

> On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
> wrote:
> Hi Ben
> Thanks for the reply.
> According to the link, in order to transfer usernames and passwords to
> SQL Server running on a different machine, the instance should be
> running under a domain account. But that is not the case with our
> setup. SQL Server is running under local machine accounts.
> Any thoughts?
> Thanks
>|||Manu
http://vyaskn.tripod.com/moving_sql_server.htm
"Manu" <mandeep.sekhon@.gmail.com> wrote in message
news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks|||On Dec 17, 3:06 am, "Uri Dimant" <u...@.iscar.co.il> wrote:[vbcol=seagreen]
> Manuhttp://vyaskn.tripod.com/moving_sql_server.htm
> "Manu" <mandeep.sek...@.gmail.com> wrote in message
> news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
>
>
>
>
Hi Uri
Thanks for the reply.
The link that you sent me requires that SQL Server be running on the
same operating system on both the machines.
In my case, however, the OS is changing too. The new machine runs
Windows Server 2003 while the older one was running Windows 2000.|||On Dec 14, 6:09 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:[vbcol=seagreen]
> Manu,
> That is only for the DTS Transfer Logins Tasks. You can still use the meth
od
> 1 of the section 'A complete resolution to transfer logins and passwords
> between different versions of SQL Server' and will get the additional bene
fit
> of transfering the original login SID.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
Hi Ben
That worked beautifully.
As mentioned on the web page, default databases assigned to the logins
are different.
Is there any way to assign the default databases apart from writing a
script using 'sp_defaultdb' for each login?
Regards

Migrate SQL 7 on W2K server to SQL 2000 on W2003 server

We are currently running SQL7 with OLAP on a windows 2000 server. I would
like to migrate everything over to a new Windows 2003 server running SQL2000.
Are their any whitepapers on such a move? Especially on migrating over the
cubes from SQL7 to SQL 2000 on a different server.
migrate to SQL 2005 w/ SP2 and cumulateive update 2187.
"nf" <nf@.discussions.microsoft.com> wrote in message
news:5BCEA93F-9BA6-461E-B9A7-F6D061C4FD7B@.microsoft.com...
> We are currently running SQL7 with OLAP on a windows 2000 server. I would
> like to migrate everything over to a new Windows 2003 server running
> SQL2000.
> Are their any whitepapers on such a move? Especially on migrating over the
> cubes from SQL7 to SQL 2000 on a different server.

Migrate SQL 7 on W2K server to SQL 2000 on W2003 server

We are currently running SQL7 with OLAP on a windows 2000 server. I would
like to migrate everything over to a new Windows 2003 server running SQL2000.
Are their any whitepapers on such a move? Especially on migrating over the
cubes from SQL7 to SQL 2000 on a different server.migrate to SQL 2005 w/ SP2 and cumulateive update 2187.
"nf" <nf@.discussions.microsoft.com> wrote in message
news:5BCEA93F-9BA6-461E-B9A7-F6D061C4FD7B@.microsoft.com...
> We are currently running SQL7 with OLAP on a windows 2000 server. I would
> like to migrate everything over to a new Windows 2003 server running
> SQL2000.
> Are their any whitepapers on such a move? Especially on migrating over the
> cubes from SQL7 to SQL 2000 on a different server.sql

Migrate Higher version of MDAC

Hi Friends,

I have a system with windows 2000 advanced server SP4 OS. In that system, How can i upgrade MDAC version from 2.5 to 2.8 sp2.

This is use of,

I am going to install sql server 2005 express edition advanced services SP2.

Please help me, how can i upgrade higher version of MDAC?

Thanks in Advance

Rameshkumar Thirumalaisamy

You just download the version you want from the Microsoft Download Center and install it. I believe that MDAC 2.8 is currently at SP1, not SP2 as you've indicated. You can find MDAC 2.8 SP1 here.

Mike

|||

Actually, if you install the SQL Server 2005 on the machine you can connect using the SNAC provider instead of using the MDAC stack. Although you should be up-to-date in the case another application needs parts of the MDAC stack.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

When installing SQL Server 2005 (any edition) on Windows 2000 there actually is a minimum version of MDAC that is required, although I can't recall what version is required, but 2.8 SP1 will certainly qualify since it's the newest. I don't know why this requirement exists only on Windows 2000.

Mike

Migrate Higher version of MDAC

Hi Friends,

I have a system with windows 2000 advanced server SP4 OS. In that system, How can i upgrade MDAC version from 2.5 to 2.8 sp2.

This is use of,

I am going to install sql server 2005 express edition advanced services SP2.

Please help me, how can i upgrade higher version of MDAC?

Thanks in Advance

Rameshkumar Thirumalaisamy

You just download the version you want from the Microsoft Download Center and install it. I believe that MDAC 2.8 is currently at SP1, not SP2 as you've indicated. You can find MDAC 2.8 SP1 here.

Mike

|||

Actually, if you install the SQL Server 2005 on the machine you can connect using the SNAC provider instead of using the MDAC stack. Although you should be up-to-date in the case another application needs parts of the MDAC stack.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

When installing SQL Server 2005 (any edition) on Windows 2000 there actually is a minimum version of MDAC that is required, although I can't recall what version is required, but 2.8 SP1 will certainly qualify since it's the newest. I don't know why this requirement exists only on Windows 2000.

Mike

migrate existing sql database to cluster

We are in the process of putting together a Windows 2000
distributed failover cluster. We have numerous SQL 2000
servers functioning as DB servers for a few different
departments. What we would like to do is eventually
migrate theses databases off of the stand alone servers to
the clustered servers.
Few questions:
Are there any major things to look out for when migrating
the databases? Or is it basically using the migration
wizard thats built into SQL server and dumping the
databases to one of the new installs of SQL on the cluster?
What about transaction and data files? Do these need to
be migrated as well?
Anything major I should be on the lookout for?
Any documentation about this on MS site? I couldnt find
any.
TIA!
Jeff BaileyYou should read on "moving databases between servers".
One Issue that often comes is security (logins/users).
"JBailey" <abc@.123.com> wrote in message
news:096701c34afd$255562c0$a001280a@.phx.gbl...
> We are in the process of putting together a Windows 2000
> distributed failover cluster. We have numerous SQL 2000
> servers functioning as DB servers for a few different
> departments. What we would like to do is eventually
> migrate theses databases off of the stand alone servers to
> the clustered servers.
> Few questions:
> Are there any major things to look out for when migrating
> the databases? Or is it basically using the migration
> wizard thats built into SQL server and dumping the
> databases to one of the new installs of SQL on the cluster?
> What about transaction and data files? Do these need to
> be migrated as well?
> Anything major I should be on the lookout for?
> Any documentation about this on MS site? I couldnt find
> any.
> TIA!
> Jeff Bailey
>|||Easiest way is probably to restore a backup to the other server
or detach/attach
INF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q224071
or use the Copy database wizard
INF: Understanding and Troubleshooting the Copy Database Wizard in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274463
Also check out
INF: How To Transfer Logins and Passwords Between SQL Servers
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q246133
PRB: User Logon and/or Permission Errors After Restoring Dump
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q168001
INF: How to Resolve Permission Issues When a Database is Moved Between SQL
Servers
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q240872
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274188
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"JBailey" <abc@.123.com> wrote in message
news:096701c34afd$255562c0$a001280a@.phx.gbl...
We are in the process of putting together a Windows 2000
distributed failover cluster. We have numerous SQL 2000
servers functioning as DB servers for a few different
departments. What we would like to do is eventually
migrate theses databases off of the stand alone servers to
the clustered servers.
Few questions:
Are there any major things to look out for when migrating
the databases? Or is it basically using the migration
wizard thats built into SQL server and dumping the
databases to one of the new installs of SQL on the cluster?
What about transaction and data files? Do these need to
be migrated as well?
Anything major I should be on the lookout for?
Any documentation about this on MS site? I couldnt find
any.
TIA!
Jeff Bailey

Migrate database from MS Access to SQL Server 2000

Hi All,
I had installed Internet Information Sevices (IIS) on
Windows 2000 to simulate a web server. The ASP code to
open the Access database is:
Set db = Server.CreateObject("ADODB.Connection")
db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
&server.MapPath("../data/test.mdb")&";"
The code works fine on IIS and Access database. Then I
installed the SQL Server 2000 and changed the ASP code to:
Set db = Server.CreateObject("ADODB.Connection")
db.open "DRIVER={SQL
Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
dbsql="Y"
Where "myPC" is the computer name, "myPasswd" is the
password for user "sa". But the ASP code did not work.
Anything wrong?
Thanks in advance.> But the ASP code did not work.
You're going to have to be more specific.|||what error do u get'
--
Shaju Thomas
"Nancy" <nlan2000@.hotmail.com> wrote in message
news:063401c39b88$7ea843c0$a301280a@.phx.gbl...
> Hi All,
> I had installed Internet Information Sevices (IIS) on
> Windows 2000 to simulate a web server. The ASP code to
> open the Access database is:
> Set db = Server.CreateObject("ADODB.Connection")
> db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
> &server.MapPath("../data/test.mdb")&";"
> The code works fine on IIS and Access database. Then I
> installed the SQL Server 2000 and changed the ASP code to:
> Set db = Server.CreateObject("ADODB.Connection")
> db.open "DRIVER={SQL
> Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
> dbsql="Y"
> Where "myPC" is the computer name, "myPasswd" is the
> password for user "sa". But the ASP code did not work.
> Anything wrong?
> Thanks in advance.
>|||Hi all,
Thanks for your kindness help.
The error message says:
HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services
Error Type:
ADODB.Recordset (0x800A0E7D)
The connection cannot be used to perform this operation.
It is either closed or invalid in this context.
Which referred to the following code:
set rs=Server.CreateObject("ADODB.Recordset")
The reason is the database connection was not set up
successfully, where the cause was actually a typo in the
server name. It works now after I corrected it.
But thanks anyway!
Nancy
>--Original Message--
>Hi All,
>I had installed Internet Information Sevices (IIS) on
>Windows 2000 to simulate a web server. The ASP code to
>open the Access database is:
>Set db = Server.CreateObject("ADODB.Connection")
>db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
>&server.MapPath("../data/test.mdb")&";"
>The code works fine on IIS and Access database. Then I
>installed the SQL Server 2000 and changed the ASP code to:
>Set db = Server.CreateObject("ADODB.Connection")
>db.open "DRIVER={SQL
>Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
>dbsql="Y"
>Where "myPC" is the computer name, "myPasswd" is the
>password for user "sa". But the ASP code did not work.
>Anything wrong?
>Thanks in advance.
>.
>|||did u open the connection
--
Shaju Thomas
"Nancy" <nlan2000@.hotmail.com> wrote in message
news:055a01c39d0b$9fc67390$a601280a@.phx.gbl...
> Hi all,
> Thanks for your kindness help.
> The error message says:
> HTTP 500.100 - Internal Server Error - ASP error
> Internet Information Services
> Error Type:
> ADODB.Recordset (0x800A0E7D)
> The connection cannot be used to perform this operation.
> It is either closed or invalid in this context.
> Which referred to the following code:
> set rs=Server.CreateObject("ADODB.Recordset")
> The reason is the database connection was not set up
> successfully, where the cause was actually a typo in the
> server name. It works now after I corrected it.
> But thanks anyway!
> Nancy
>
> >--Original Message--
> >Hi All,
> >
> >I had installed Internet Information Sevices (IIS) on
> >Windows 2000 to simulate a web server. The ASP code to
> >open the Access database is:
> >
> >Set db = Server.CreateObject("ADODB.Connection")
> >db.open "Driver={Microsoft Access Driver (*.mdb)}; DBQ="
> >&server.MapPath("../data/test.mdb")&";"
> >
> >The code works fine on IIS and Access database. Then I
> >installed the SQL Server 2000 and changed the ASP code to:
> >
> >Set db = Server.CreateObject("ADODB.Connection")
> >db.open "DRIVER={SQL
> >Server};SERVER=myPC;UID=sa;PWD=myPasswd;DATABASE=test"
> >dbsql="Y"
> >
> >Where "myPC" is the computer name, "myPasswd" is the
> >password for user "sa". But the ASP code did not work.
> >
> >Anything wrong?
> >
> >Thanks in advance.
> >
> >.
> >

Microsoft.VC80.CRT.mui

I have SQL 2005, 64bit version installed with SP1. I am seeing the following
errors in the Windows event log:
Source: SideBySide Event ID: 59
Resolve Partial Assembly failed for Microsoft.VC80.CRT.mui. Reference error
message: Access is denied.
Source: SidebySide EventID: 59
Generate Activation Context failed for D:\Program Files\Microsoft SQL
Server\MSSQL.2\OLAP\bin\msmdctr90.DLL. Reference error message: Access is
denied.
Source: PerfLib EventID: 1023
Windows cannot load extensible counter DLL MSSQLServerOLAPService, the first
DWORD in data section is the Windows error code.
Does anyone know what the problem is?
Thanks
--
LehrSJHello LehrSJ,
I understand that you found some SQL related events on a SQL 2005 SP1 64bit
server, and you'd like to know what this problem is.
Based on my experience, this issue could occur if the "Performance Logs and
Alerts" service runs as "Network Service", which is member of "Performance
Log Users" local user group, does not have enough permission to SQL setup
folder.
SQL Setup grants read/execute permissions to "Performance Log Users" local
user group for the DLL only. "Performance Log Users" doesn?t have any
permissions for the containing folder. Granting "List folder contents"
permission to "Performance Log Users" for the containing folder (SQL Server
binn directory) may fix this problem:
D:\Program Files\Microsoft SQL Server\MSSQL.1\mssql\bin
D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin
If you have any update or the issue is not resolved, please feel free to
let's know. I look forward to your reply.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks. That solved the problem.
--
LehrSJ
""privatenews"" wrote:
> Hello LehrSJ,
> I understand that you found some SQL related events on a SQL 2005 SP1 64bit
> server, and you'd like to know what this problem is.
> Based on my experience, this issue could occur if the "Performance Logs and
> Alerts" service runs as "Network Service", which is member of "Performance
> Log Users" local user group, does not have enough permission to SQL setup
> folder.
> SQL Setup grants read/execute permissions to "Performance Log Users" local
> user group for the DLL only. "Performance Log Users" doesnâ't have any
> permissions for the containing folder. Granting "List folder contents"
> permission to "Performance Log Users" for the containing folder (SQL Server
> binn directory) may fix this problem:
> D:\Program Files\Microsoft SQL Server\MSSQL.1\mssql\bin
> D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin
> If you have any update or the issue is not resolved, please feel free to
> let's know. I look forward to your reply.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||I was having this problem as well on a 32 bit system and that fixed it.
Can you explain why that fixed it? I'm asking because I was also having
2 other problems that I think this fixed as well.
first one: There is a Java program that inserts updates and deletes
records in a very large table on the sql server. It spawns 12 processes
that each have a connection to the DB and every time this program ran,
2 of them would hang up and would not receive any errors. I looked and
they were no longer connected.
second one: The users of this server have pocket pcs that connect using
sql ce server with RDA. They use an app that we wrote to replicate
their data. Along with all the pushing and pulling of tables, there is
one stored procedure that the client runs on the server. Apparently
randomly this stored procedure stops working for about 30 minutes at a
time. What happens on the client is when it calls that sp, it just
hangs there maintaining it's connection until all the sudden the sp
start working again. During the 30 minutes nobody can run the sp.
Both of these problems did not exist before we got Error 59 or after it
was fixed.
Does anybody have any clue as to why this would fix these 2 problems or
has anybody experienced anything like this?
thanks,
cob