Migrating from Enterprise to SQL Server 2000 Standard

We are migrating a browser based application developed
with the Enterprise version to a server running the
standard edition. There will be some development on the
standard version before a new vresion of the application
is deployed. Can anyone help me to understand what
issues/problems we should look out for?Since most of the difference between Standard Edition and Enterprise Edition
involves scalability and availability features (>4 processors, large memory
support, clusters) there generally will be no problems migrating
applications from Enterprise to Standard. The few small gotchas include
Transparent Materialized Views and Distributed Partitioned Views, both of
which are only included in Enterprise Edition. (For completeness, Analysis
Services has some similar differences between Standard and Enterprise). If
you have not used these few scalability-related features then you will not
notice application level differences between these editions.
See "Features Supported by the Editions of SQL Server 2000" in Books Online.
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"rez" <rezam@.go.com> wrote in message
news:039601c37bc5$bda02a30$a401280a@.phx.gbl...
> We are migrating a browser based application developed
> with the Enterprise version to a server running the
> standard edition. There will be some development on the
> standard version before a new vresion of the application
> is deployed. Can anyone help me to understand what
> issues/problems we should look out for?

migrating form standard to enterprise edition

Hi,

Can someone tell me what the best way is to migrate from a SQL Server 2000
Standard Edition to a SQL Server 2000 Enterprise Edition?
Is this a migration possible from the setup program of the Enterprise
Edition?
What are the pitfalls?

Thanks in advance
Theo LinnenbankTheo Linnenbank (theo@.totalweb.nl) writes:
> Can someone tell me what the best way is to migrate from a SQL Server 2000
> Standard Edition to a SQL Server 2000 Enterprise Edition?
> Is this a migration possible from the setup program of the Enterprise
> Edition?

Yes. See Books Online, Installing SQL Server -> Upgrading an Existing
Installation of SQL Server.

> What are the pitfalls?

As a safety precaution, I would re-apply the latest service pack.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsql

Migrating Enterprise Manager Server List

Hi All,
I have just installed EM for SQL Server 2000 and so have no registered servers in the console list. We have about 50 servers which we support and so I would rather import my colleagues list rather than registering them all manually. Is there ay way to do this ?
Many thanks
AndyUSE THIS AT YOUR OWN RISK. Works for me !! I accept no responsibility for anything :)

Well, this is a solution I would not attribute to myself , coz i did never invent it myself.

Register all your servers in one Enterprise Manager.

Then go to these keys :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\SuperSocketNetLib\LastConnect]

[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQLEW\Registered Servers X]


and export them.

Share the .reg files with your colleagues. Enjoy|||Enigma,
Thanks a lot... this worked a treat.
Cheers
Andysql

migrating db

I have an ms sql 2000 db which I am migrating from one shared environment to another. How specifcally can I do this?

I have a copy of enterprise but not a full version of SQL on my local desktop.
The hosting company from which I am moving has placed the db as a zip file on the root of my site via ftp. I have unzipped it and it appears as a backup copy (.bak).

I appreciate any detail steps, I assume via enterprise, that anyone can give me. Thank you.Create a database on your server, and then restore the backup to it.
For detailed steps, see Books Online.

Migrating a single SQL2K Install to a SQL Clustered install.

Is it possible to to migrate a single standalone installation of SQL 2000
Enterprise Edition to be part of a clustered SQL installation. My initial
guess is that as SQL installs by default registering to the Server IP
address, and a clustered install requires its own IP address to be installed
under. Therefore I would have to unistall any SQL install and start from
scratch?
ThanksHi
You are correct, you first ahve to un-install and re-install. No other way.
Regards
Mike
"Siz Choudhury" wrote:
> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be installed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks|||Be sure to back up all of your databases, so can restore them to the
cluster..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Siz Choudhury" <Siz Choudhury@.discussions.microsoft.com> wrote in message
news:E14A249A-0E2B-467D-80B6-BFCDE8B9C778@.microsoft.com...
> Is it possible to to migrate a single standalone installation of SQL 2000
> Enterprise Edition to be part of a clustered SQL installation. My initial
> guess is that as SQL installs by default registering to the Server IP
> address, and a clustered install requires its own IP address to be
installed
> under. Therefore I would have to unistall any SQL install and start from
> scratch?
> Thanks

Migrate SQL2005 from Standard to Enterprise edition

Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise editio
n ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one o
f
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.Hi
"Johnny" wrote:

> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edit
ion ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one
of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/li...aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/li...x#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/li...aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/li...x#reinstallmode and t
he
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John|||Hi
"Johnny" wrote:

> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means tha
t
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>|||Hi
"Johnny" wrote:

> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
John

Migrate SQL2005 from Standard to Enterprise edition

Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.
Hi
"Johnny" wrote:

> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John
|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John
|||Hi
"Johnny" wrote:

> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John
|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:

> Hi
> "Johnny" wrote:
>
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>
|||Hi
"Johnny" wrote:

> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
John

Migrate SQL2005 from Standard to Enterprise edition

Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.Hi
"Johnny" wrote:
> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> >
> > I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> > prompted the following message after a few step.
> >
> > "To change existing instance of SQL2005 to a different edition of SQL2005,
> > you must run SQL2005 Setup from the command prompt and include the
> > SKUUPGRADE=1 parameter".
> >
> > Followed the instruction to run setup with the parameter, upgraded
> > successfully but it got error when I started SSMS.
> >
> > "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> > Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> > its dependencies. The system could not find the file specified."
> >
> > End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> > Looking forward to your advices.
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John|||Hi
"Johnny" wrote:
> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Hi John,
> >
> > I wish to clarify that upgrading the edition has to specify
> > UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> > the client tools is no need for the edition upgrade (only sql_engine is
> > required.)
> >
> > Johnny
> > "John Bell" wrote:
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>|||Hi
"Johnny" wrote:
> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
Johnsql

Migrate from non-cluster to Cluster

I have a single SQL 2000 Enterprise server and I need to turn it into a
cluster. We have several applications using SQL, so the hostname and
configuration of the cluster must be the same as the existing single server.
The operating system is WS2003E and they are in a AD domain.
Is there a fairly easy migration path from a single to clustered
configuration, or do I have to setup two new servers and somehow get the
cluster to use the old hostname? Do I just do a SQL backup of the old
server, power it off, setup the cluster using the old hostname and then do a
SQL restore? I need to minimize downtime and I can't reconfigure the
applications to point to another SQL server.
Do I register the SPNs for the virtual hostname of the cluster?
Thanks,
Derek
Reusing the name is not really an option for several reasons (AD name
conflict, DNS name conflict, SQL cluster naming options). You can use DNS to
alias the old name to the new name.
While it is possible to migrate a non-clustered instance to a clustered
instance, I would recommend setting up a new system. That way if anything
goes wrong, your existing system is right there to pick up and run. Failure
isn't so painful. You can use manual log shipping or a simple log shipping
script to minimize downtime by getting your new server 'close' to the old
one. Be sure and plan the cutover process and test it (maybe in a smaller
scale using a couple of SQL instances on a test box).
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Derek" <dseaman@.spawar.navy.mil> wrote in message
news:ep1mEXCyEHA.3584@.TK2MSFTNGP10.phx.gbl...
> I have a single SQL 2000 Enterprise server and I need to turn it into a
> cluster. We have several applications using SQL, so the hostname and
> configuration of the cluster must be the same as the existing single
server.
> The operating system is WS2003E and they are in a AD domain.
> Is there a fairly easy migration path from a single to clustered
> configuration, or do I have to setup two new servers and somehow get the
> cluster to use the old hostname? Do I just do a SQL backup of the old
> server, power it off, setup the cluster using the old hostname and then do
a
> SQL restore? I need to minimize downtime and I can't reconfigure the
> applications to point to another SQL server.
> Do I register the SPNs for the virtual hostname of the cluster?
> Thanks,
> Derek
>
>
|||How about if I backup the non-clustered server, remove it from AD, and built
up a cluster with the virtual name being the name of the old SQL server and
then do a SQL restore? We have too many apps to be changing the name, and I
hate to play tricks with DNS that are prone to human error.
Derek
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:eKaQfWDyEHA.1188@.tk2msftngp13.phx.gbl...
> Reusing the name is not really an option for several reasons (AD name
> conflict, DNS name conflict, SQL cluster naming options). You can use DNS
> to
> alias the old name to the new name.
> While it is possible to migrate a non-clustered instance to a clustered
> instance, I would recommend setting up a new system. That way if anything
> goes wrong, your existing system is right there to pick up and run.
> Failure
> isn't so painful. You can use manual log shipping or a simple log
> shipping
> script to minimize downtime by getting your new server 'close' to the old
> one. Be sure and plan the cutover process and test it (maybe in a smaller
> scale using a couple of SQL instances on a test box).
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Derek" <dseaman@.spawar.navy.mil> wrote in message
> news:ep1mEXCyEHA.3584@.TK2MSFTNGP10.phx.gbl...
> server.
> a
>
|||Try this in a test environment first.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Derek" <dseaman@.spawar.navy.mil> wrote in message
news:uyD4T%23czEHA.3336@.TK2MSFTNGP11.phx.gbl...
> How about if I backup the non-clustered server, remove it from AD, and
built
> up a cluster with the virtual name being the name of the old SQL server
and
> then do a SQL restore? We have too many apps to be changing the name, and
I[vbcol=seagreen]
> hate to play tricks with DNS that are prone to human error.
> Derek
>
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:eKaQfWDyEHA.1188@.tk2msftngp13.phx.gbl...
DNS[vbcol=seagreen]
anything[vbcol=seagreen]
old[vbcol=seagreen]
smaller[vbcol=seagreen]
the
>

Migrate DTC

Hi guys,
I have an existing sql 2k enterprise server and we're going to configure it
for server clustering. We have custom made DTC package and most of the
application use it very often.
My concern is how do we migrate this custom made DTC package to the new
environment(sql cluster)?
Appreaciate ur guys help.
Hidayat
Message posted via http://www.droptable.com
I maybe missing something; due my true lack of understanding MSDTC, but I
don't think you have anything to migrate. MSDTC as far as I know, is just a
log file, and a new install will use a new log file. This should be a walk
in the park.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.nospam.droptable.com> wrote in message
news:4FE03924D8C20@.droptable.com...
> Hi guys,
> I have an existing sql 2k enterprise server and we're going to configure
> it
> for server clustering. We have custom made DTC package and most of the
> application use it very often.
> My concern is how do we migrate this custom made DTC package to the new
> environment(sql cluster)?
> Appreaciate ur guys help.
> Hidayat
> --
> Message posted via http://www.droptable.com
|||tks for your prompt reply.
Another question i would like to ask is do we need different virtual ip for
MSDTC & SQL cluster? Can we use the existing virtual ip that we configure for
MSCS?
Tks
Message posted via http://www.droptable.com
|||If MSDTC has heavy usage then give it its own Group - with an Virtual IP,
Virtual Name, Physical Disk, and the MSDTC resource. If it is not a heavy
hitter, then don't worry about it.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FE4339FB56C0@.droptable.com...
> tks for your prompt reply.
> Another question i would like to ask is do we need different virtual ip
> for
> MSDTC & SQL cluster? Can we use the existing virtual ip that we configure
> for
> MSCS?
> Tks
> --
> Message posted via http://www.droptable.com
|||Can the physical disk for MSDTC be the same(sharing) for the SQL cluster
physical disk?
In SQL cluster environment, how is the procedure of restoring the database?
Is it the same as normal SQL restore using it's own utility. As i know the
data will centrally reside in the SAN(EMC) storage.
Tks
Message posted via http://www.droptable.com
|||You can share the space. But if it is heavily used that maybe a bad idea.
Everything about a database is the same, restore, attach, etc. The Books
Online are wonderful and full of great information.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FE89EBC9A9E0@.droptable.com...
> Can the physical disk for MSDTC be the same(sharing) for the SQL cluster
> physical disk?
> In SQL cluster environment, how is the procedure of restoring the
> database?
> Is it the same as normal SQL restore using it's own utility. As i know the
> data will centrally reside in the SAN(EMC) storage.
> Tks
> --
> Message posted via http://www.droptable.com
|||Clustered SQL servers look and act just like normal SQL servers for amost
every purpose, including backup and restore. There are some extra steps for
things like restoring master, adding disks, and adding/dropping cluster
nodes but these are well documented. From the client's point of view, they
look and act exactly like any other SQL server.
Geoff N. Hiten
Microsoft SQL Server MVP
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FE89EBC9A9E0@.droptable.com...
> Can the physical disk for MSDTC be the same(sharing) for the SQL cluster
> physical disk?
> In SQL cluster environment, how is the procedure of restoring the
> database?
> Is it the same as normal SQL restore using it's own utility. As i know the
> data will centrally reside in the SAN(EMC) storage.
> Tks
> --
> Message posted via http://www.droptable.com
|||Tks for the explaination. Just to confirm with u guys. Let's say that i have
2 node(A & B). I install and configure SQL cluster on Node A. Must i install
the SQL cluster on Node B?
Message posted via http://www.droptable.com
|||Tks a million guys. Let's say that i have 5GB each on 2 servers. Should i
enabled /3GB or /PAE or AWE? What is u guys best recommendation. I'm going to
configure clustering this Saturday and will be in production.
This clustering is new to me so tks for your patient in answering my question.
U guys have been very helpful.
Tks.
Message posted via http://www.droptable.com
|||Great question. You need to 1) talk to you hardware vendor and find out if
/PAE or /AWE are even supported. 2) test the /3GB with whatever the vendor
supports, you may not see any difference or worse, things could get slower,
3) I am guessing you will only need /PAE to see the 5 GB of memory, but this
is a guess - testing will tell all.
Lastly, you are on a very aggressive schedule. It sounds like you need more
testing time to me BEFORE you go live. This being your first cluster, can
you restore it or a node in the case of a failure? Do you fully understand
how to handle service packs, etc. I am not trying to beat you up, you have a
learning curve ahead. After you in production is really not the way to
manage and maintain your Highly Available SQL Failover Cluster.
Just my two cents...
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
"Hidayat via droptable.com" <forum@.droptable.com> wrote in message
news:4FF0A99441520@.droptable.com...
> Tks a million guys. Let's say that i have 5GB each on 2 servers. Should i
> enabled /3GB or /PAE or AWE? What is u guys best recommendation. I'm going
> to
> configure clustering this Saturday and will be in production.
> This clustering is new to me so tks for your patient in answering my
> question.
>
> U guys have been very helpful.
> Tks.
> --
> Message posted via http://www.droptable.com

Migrate Data Bases Different Server

Hi!!!
I have 2 servers running sql server enterprise 2000, however I will
shutdown one of them and will use only the newest.
I have to migrate 2 databases.. I was wondering which is the best way to do
so..
I thought that I can make a full backup and then restore the backup on the
new server but I dont know if this is possible...
or is there another way to do so? is it dangerous? easy?
Thanxs and
Greetings =)
http://support.microsoft.com/?kbid=224071
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
do
> so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>
|||Backup & Restore or attach & detach are usually the easiest but you might
want to have a look at these:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://www.databasejournal.com/featu...le.php/3379901 Moving
system DB's
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://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
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/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
> do so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>
|||HI!!!
Thanxs a lot that really really helped =)
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
> do so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>
|||Or use DTS
Or use DataStudio from our company, check our website right here.
http://www.agileinfollc.com
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:OO8Rj1zoFHA.576@.TK2MSFTNGP15.phx.gbl...
> HI!!!
> Thanxs a lot that really really helped =)
>
> "Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
> news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
>

Migrate Data Bases Different Server

Hi!!!
I have 2 servers running sql server enterprise 2000, however I will
shutdown one of them and will use only the newest.
I have to migrate 2 databases.. I was wondering which is the best way to do
so..
I thought that I can make a full backup and then restore the backup on the
new server but I dont know if this is possible...
or is there another way to do so? is it dangerous? easy?
Thanxs and
Greetings =)http://support.microsoft.com/?kbid=224071
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Jesús Gutiérrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
do
> so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>|||Backup & Restore or attach & detach are usually the easiest but you might
want to have a look at these:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's
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://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
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
Andrew J. Kelly SQL MVP
"Jesús Gutiérrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
> do so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>|||Hi,
U can by many ways have a look on all those links.
U can all do by copy database wizard, Attach and detach.Restore backup.
In copy database wizard u will get the in time data.
hope this help
from
killer|||HI!!!
Thanxs a lot that really really helped =)
"Jesús Gutiérrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
> do so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>|||Or use DTS
Or use DataStudio from our company, check our website right here.
http://www.agileinfollc.com
"Jesús Gutiérrez" <ardillapaw@.msn.com> wrote in message
news:OO8Rj1zoFHA.576@.TK2MSFTNGP15.phx.gbl...
> HI!!!
> Thanxs a lot that really really helped =)
>
> "Jesús Gutiérrez" <ardillapaw@.msn.com> wrote in message
> news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
>> Hi!!!
>> I have 2 servers running sql server enterprise 2000, however I will
>> shutdown one of them and will use only the newest.
>> I have to migrate 2 databases.. I was wondering which is the best way to
>> do so..
>> I thought that I can make a full backup and then restore the backup on
>> the new server but I dont know if this is possible...
>> or is there another way to do so? is it dangerous? easy?
>> Thanxs and
>> Greetings =)
>>
>

Migrate Data Bases Different Server

Hi!!!
I have 2 servers running sql server enterprise 2000, however I will
shutdown one of them and will use only the newest.
I have to migrate 2 databases.. I was wondering which is the best way to do
so..
I thought that I can make a full backup and then restore the backup on the
new server but I dont know if this is possible...
or is there another way to do so? is it dangerous? easy?
Thanxs and
Greetings =)http://support.microsoft.com/?kbid=224071
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
do
> so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>|||Backup & Restore or attach & detach are usually the easiest but you might
want to have a look at these:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's
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://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
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
Andrew J. Kelly SQL MVP
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
> do so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>|||HI!!!
Thanxs a lot that really really helped =)
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Hi!!!
> I have 2 servers running sql server enterprise 2000, however I will
> shutdown one of them and will use only the newest.
> I have to migrate 2 databases.. I was wondering which is the best way to
> do so..
> I thought that I can make a full backup and then restore the backup on the
> new server but I dont know if this is possible...
> or is there another way to do so? is it dangerous? easy?
> Thanxs and
> Greetings =)
>
>|||Or use DTS
Or use DataStudio from our company, check our website right here.
http://www.agileinfollc.com
"Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
news:OO8Rj1zoFHA.576@.TK2MSFTNGP15.phx.gbl...
> HI!!!
> Thanxs a lot that really really helped =)
>
> "Jess Gutirrez" <ardillapaw@.msn.com> wrote in message
> news:%23$3Ar7coFHA.3936@.TK2MSFTNGP10.phx.gbl...
>

Microsoft SQL Server Management Studio

I have recently moved from a Microsoft SQL Server 2000 to a SQL Server
2005.
In the good old Enterprise Manager, when I imported a table from a SQL
server to another, I could choose "Copy objects and data between SQL
Server
databases". When choosen, all primary keys, and default values was
copied.
My question is:
Is it possible to do the same in Microsoft SQL Server Management Studio
with
SQL Server 2005? And how do I do it?
I have tried using the "SELECT * INTO NewTable FROM OldTable"
statement, but
it just drops all information about primary keys and default values.
Best Regards
Right click on the database in Object Explorer and choose "All Tasks". Then
choose export and follow the wizard.
Andrew J. Kelly SQL MVP
<pd@.acskive.dk> wrote in message
news:1143018478.487953.10000@.i40g2000cwc.googlegro ups.com...
>I have recently moved from a Microsoft SQL Server 2000 to a SQL Server
> 2005.
> In the good old Enterprise Manager, when I imported a table from a SQL
> server to another, I could choose "Copy objects and data between SQL
> Server
> databases". When choosen, all primary keys, and default values was
> copied.
> My question is:
> Is it possible to do the same in Microsoft SQL Server Management Studio
> with
> SQL Server 2005? And how do I do it?
> I have tried using the "SELECT * INTO NewTable FROM OldTable"
> statement, but
> it just drops all information about primary keys and default values.
>
> Best Regards
>

Microsoft SQL Server maintenance plan

On a server running Windows NT 4.0 and Microsoft SQL Server 7 I have set up a database maintenance plan through Enterprise Manager to perform backups, database consistency checks and update statistics. The job fails to start and Event ID:208 is generated within the application log component of the event viewer log. I have set the SqlServerAgent service to start as user sqlservice, a user with administrator rights and as the system account and have logged in as these accounts to run the maintenance plan jobs with the same result.

I have performed this task before on a number of servers without encountering this problem.

ThanksDoes this also occur if you:
specify the sa account or equivalent (if running mixed authentication), use local administrator equivalent accounts,
use domain administrator equivalent accounts?

Also, did you also stop and start the services following each account change?|||Originally posted by DBA
Does this also occur if you:
specify the sa account or equivalent (if running mixed authentication), use local administrator equivalent accounts,
use domain administrator equivalent accounts?

Also, did you also stop and start the services following each account change?

Have used the sa account, domain administrator equivalent account and local administrator equivalent account with same result.

Services were cycled after each change.|||This is not helpful but at this point it could possibly be an issue of maint dlls becomming corrupt / unregistered, etc., some kind of security issue, a service pack or hot fix issue (up to date?), or something else entirely. Some things to think about may include:
Do any maint jobs run? Have any ever run sucesfully? Do non-maint jobs run fine? What is common about those that do / do not? Is the server stand alone, domain member DC, etc. (what kind of domain, any domain issues going on, etc.)? You may wish to try some interactive testing, have you tried:
copying the information from each maint. job into QA and running it interactively from QA with different accounts (note successes, failures, error messages, run a profile / trace while doing so for any that do not immediatly fail.)|||Originally posted by DBA
This is not helpful but at this point it could possibly be an issue of maint dlls becomming corrupt / unregistered, etc., some kind of security issue, a service pack or hot fix issue (up to date?), or something else entirely. Some things to think about may include:
Do any maint jobs run? Have any ever run sucesfully? Do non-maint jobs run fine? What is common about those that do / do not? Is the server stand alone, domain member DC, etc. (what kind of domain, any domain issues going on, etc.)? You may wish to try some interactive testing, have you tried:
copying the information from each maint. job into QA and running it interactively from QA with different accounts (note successes, failures, error messages, run a profile / trace while doing so for any that do not immediatly fail.)

This problem has now been resolved, further research led me to discover that the sqlmaint executable on this server was missing. I do not know the reason for this however as soon as I placed a copy in the Microsoft SQL Server binn directory, I was able to successfully execute the maintenance plan jobs.

Thank you for your prompt assistance.|||RE:
This problem has now been resolved, further research led me to discover that the sqlmaint executable on this server was missing. I do not know the reason for this however as soon as I placed a copy in the Microsoft SQL Server binn directory, I was able to successfully execute the maintenance plan jobs.

Thank you for your prompt assistance.

You are welcome.

It is kind of interesting that: "the sqlmaint executable on this server was missing"; I remember some similar complaints about issues with sql maint plans failing to execute that were apparently addressed by overwriting the sqlmaint files (exe, rll, etc). That was what led me to mention that it might possibly be an issue of corrupted maint exe, rlls, etc. (makes one wonder if something, or some rarely performed process corrupts and / or deletes them).