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 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 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 Access XP database to SQL Server 2005 Express

I want to migrate my Access XP database to SQL Server 2005 Express Edition. The Start Menu does not display any migration assistant in SQL Server 2005 Express menu list.

How to migrate it?

hi,

never tried it my self, but have a look at http://www.microsoft.com/downloads/details.aspx?familyid=D842F8B4-C914-4AC7-B2F3-D25FFF4E24FB&displaylang=en

regards

|||

Access includes a tool called the upsizing wizard that will assist in moving your database to SQL.

Regards,

Mike

Migrating Access XP database to SQL Server 2005 Express

I want to migrate my Access XP database to SQL Server 2005 Express Edition. The Start Menu does not display any migration assistant in SQL Server 2005 Express menu list.

How to migrate it?

hi,

never tried it my self, but have a look at http://www.microsoft.com/downloads/details.aspx?familyid=D842F8B4-C914-4AC7-B2F3-D25FFF4E24FB&displaylang=en

regards

|||

Access includes a tool called the upsizing wizard that will assist in moving your database to SQL.

Regards,

Mike

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?
Thanks
Hi
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
sql

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

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 install
ed
> 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 to Compact Edition

What is the fastest way to migrate a database from SQL server express to sql compact edition. My database includes one stored procedure. Do I have to rewrite it into the code of my application?You can use some of the tools from www.primeworks-mobile.com (Data Port Wizard, for example) and yes, stored procedures does not exist in SQL Compact, so you will have to rewrite it as procedural code.|||

It looks fantastic, but it fails when I try to connect it to a SQL compact database even it does not have a password

Migrate to Compact Edition

What is the fastest way to migrate a database from SQL server express to sql compact edition. My database includes one stored procedure. Do I have to rewrite it into the code of my application?You can use some of the tools from www.primeworks-mobile.com (Data Port Wizard, for example) and yes, stored procedures does not exist in SQL Compact, so you will have to rewrite it as procedural code.|||

It looks fantastic, but it fails when I try to connect it to a SQL compact database even it does not have a password

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 ASP .net web site from sql 2005 express to sql 2005 standard edition

Dear all,

I've been using ASP.NET with SQL 2005 express for several months and everything has been fine. Now a customer asks me to install my application on an already existant instance of SQL Server standard edition.

I was not able to use nor my application, neither a HelloWorld example.

I created a simple Default.aspx that uses a simple database with a single table "Person" via a standard gridview. When I try to open the page I receive an error wich informs me that NT Network service is not able to access database.

I've been searching on google for hours and I've tryed unsuccessfully several different way.

Can anyone suggest me a scientific procedure to migrate an ASP .net web site from sql 2005 express to sql 2005 standard ?

Thank you very Much

Fabrizio

As I know the only think you have to change is a connection string because SQL express uses different syntax for it. You can move your database to SQL server standard just by connecting it to server, you have to create your users and give them correct rights, you also have to create ASP DB if you would like to use ASP authentication finally modify your connections stirings to point to SQL server not to local SQL server express file.

There are a lot of post about this on this ASP forum.

Good luck

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ? I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks.....
Users group or newsgroup?
For newsgroups, try:
microsoft.public.windowsxp.help_and_support
-Sue
On Mon, 15 Nov 2004 11:20:44 -0800, "Dan"
<anonymous@.discussions.microsoft.com> wrote:

>Sorry for this post but can anyone direct me to Windows XP
>Home edition user group ? I Think I locked myself out of
>my computer unless Installing SP2 messed me up which is
>not installed at all......
>Thanks.....

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ? I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks.....
"Dan" <anonymous@.discussions.microsoft.com> wrote in news:5be201c4cb48
$325c2540$a401280a@.phx.gbl:

> Sorry for this post but can anyone direct me to Windows XP
> Home edition user group ? I Think I locked myself out of
> my computer unless Installing SP2 messed me up which is
> not installed at all......
> Thanks.....
>
alt.os.windows-xp

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ' I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks....."Dan" <anonymous@.discussions.microsoft.com> wrote in news:5be201c4cb48
$325c2540$a401280a@.phx.gbl:

> Sorry for this post but can anyone direct me to Windows XP
> Home edition user group ' I Think I locked myself out of
> my computer unless Installing SP2 messed me up which is
> not installed at all......
> Thanks.....
>
alt.os.windows-xp

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ' I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks.....Sorry for the double post......
>--Original Message--
>Sorry for this post but can anyone direct me to Windows
XP
>Home edition user group ' I Think I locked myself out of
>my computer unless Installing SP2 messed me up which is
>not installed at all......
>Thanks.....
>.
>|||Users group or newsgroup?
For newsgroups, try:
microsoft.public.windowsxp.help_and_support
-Sue
On Mon, 15 Nov 2004 11:20:44 -0800, "Dan"
<anonymous@.discussions.microsoft.com> wrote:
>Sorry for this post but can anyone direct me to Windows XP
>Home edition user group ' I Think I locked myself out of
>my computer unless Installing SP2 messed me up which is
>not installed at all......
>Thanks.....

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ' I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks....."Dan" <anonymous@.discussions.microsoft.com> wrote in news:5be201c4cb48
$325c2540$a401280a@.phx.gbl:
> Sorry for this post but can anyone direct me to Windows XP
> Home edition user group ' I Think I locked myself out of
> my computer unless Installing SP2 messed me up which is
> not installed at all......
> Thanks.....
>
alt.os.windows-xp

Microsoft Update & SP1

Hi,
I recently upgraded to SQL Server 2005 SP1 (developer edition) on WinXP Pro
+ SP2 by using the Microsoft Update service.
No issues were noted during the upgrade process, and EXEC master..xp_msver
returns 9.00.2047.00 in the ProductVersion column.
However, subsequent running of Microsoft Update still shows SQL Server 2005
SP1 (KB913090) as needing to be installed.
Is this a bug with Microsoft Update, or does it mean that SP1 isn't
installed properly?
Any assistance gratefully received.
MarkHi Mark
It looks like you are on SP1 on that instance! Do you have multiple
instances on this machine? Did you check the installation's log files
(hopefully this is going to be in the same place as a manual installation!).
Have you rebooted since the upgrade?
If you are confident that it is upgraded then you could choose the option to
not show the update again when the update details are expanded.
John
"Mark Rae" wrote:

> Hi,
> I recently upgraded to SQL Server 2005 SP1 (developer edition) on WinXP Pr
o
> + SP2 by using the Microsoft Update service.
> No issues were noted during the upgrade process, and EXEC master..xp_msver
> returns 9.00.2047.00 in the ProductVersion column.
> However, subsequent running of Microsoft Update still shows SQL Server 200
5
> SP1 (KB913090) as needing to be installed.
> Is this a bug with Microsoft Update, or does it mean that SP1 isn't
> installed properly?
> Any assistance gratefully received.
> Mark
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:34B375F1-9334-4141-B282-2FB06C8D4A44@.microsoft.com...

> Do you have multiple instances on this machine?
No.

> Did you check the installation's log files (hopefully this is going to be
> in the same place as a manual installation!).
Yes.

> Have you rebooted since the upgrade?
Yes. And reapplied the upgrade. And rebooted after that.

> If you are confident that it is upgraded
I'm as confident as I can be, I suppose. Other than master..xp_msver /
SELECT @.@.VERSION, is there anything else I can try...?

> then you could choose the option to not show the update again
> when the update details are expanded.
Yes, but I was loathe to do that until I'd at least asked in here. I've done
a Google search, and there doesn't seem to be anything about this specific
issue. Lots about SP1, of course, but nothing relating to problems with
applying it through Microsoft Update.
I should receive SP1 on DVD any day now as part of my MSDN Universal
subscription, so I'll reinstall it from that and then remove the option from
Microsoft Update if that doesn't fix it.