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?
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Friday, March 30, 2012
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
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
Friday, March 23, 2012
Migrate stand alone sql server to a cluster without downtime
Hi
I have read most the articles and posts about move sql server.
Here is my situation:
I have stand alone standard sql server 2000 and with about 40 databases. And
I am moving the server to a SQL cluster(Active/passive). I have to use the
old name, IP on the new server and with minimum down time. Anybody has done
this? What is the precedure? Will Virutas BackupExe backup/restore work? I
know Deattach/Reattach works but I have to do it one DB at a time, right?
That will take a long time. Will permission be carried over using these
mothed?
Any information will be greatly appreciated.
Thanks,
Yuhong
First, you cannot use the same name and IP address. The cluster
installation and any data transfer will fail.
Here is how you do this.
First, make sure all your SQL connections to the old box use a DNS entry to
resolve their names. Eliminate any hard-coded IP addresses by using client
aliases if necessary. You will use an SVC record in the DNS system to
repoint the old connections to the new server when you do the changeover.
Test this using a bogus alias before going live.
Set all your production databases to full recovery and implement a log
backup plan.
Use backup and restore to create the databases on the new system. Use the
'NORECOVERY' or 'STANDBY' option so you can apply later transaction logs.
Manually copy and apply the transaction log backups from the old system to
the new cluster.
I suggest scripting the following tasks well ahead of time.
Run a log backup WITH STANDBY on each database on the old server. Copy the
files (or restore from a common network share) and restore the final log for
each database using the WITH RECOVERY option.
When you have transferred the final database log, use sp_change_users_login
to remap your pre-generated logins to the users in the restored databases.
I typically use a bogus password for SQL logins until this step so that
users cannot accidentally connect to the new server.
Stop the old server. Add the SVC record to DNS to alias the old servername
to the new service. Remember to include the port number if you are using a
named instance or a non-standard port.
Get ready to deal with the handful of systems you missed that are still
connecting via IP.
Remember to test everything before going live. If you mess up, you can
always bring the old server back up and take the databases out of standby to
get back to where you started. The actual changeover should take less than
one hour IF you plan, test, and practice.
Good luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
news:59B178D2-D730-4142-BE76-E0A38FE53F69@.microsoft.com...
> Hi
> I have read most the articles and posts about move sql server.
> Here is my situation:
> I have stand alone standard sql server 2000 and with about 40 databases.
And
> I am moving the server to a SQL cluster(Active/passive). I have to use the
> old name, IP on the new server and with minimum down time. Anybody has
done
> this? What is the precedure? Will Virutas BackupExe backup/restore work? I
> know Deattach/Reattach works but I have to do it one DB at a time, right?
> That will take a long time. Will permission be carried over using these
> mothed?
> Any information will be greatly appreciated.
> Thanks,
> --
> Yuhong
|||Thanks, Geoff! This is very helpful. I have setup a test cluster and I will
have to do a few full test before the real migration.
Thanks again!
Yuhong
"Geoff N. Hiten" wrote:
> First, you cannot use the same name and IP address. The cluster
> installation and any data transfer will fail.
> Here is how you do this.
> First, make sure all your SQL connections to the old box use a DNS entry to
> resolve their names. Eliminate any hard-coded IP addresses by using client
> aliases if necessary. You will use an SVC record in the DNS system to
> repoint the old connections to the new server when you do the changeover.
> Test this using a bogus alias before going live.
> Set all your production databases to full recovery and implement a log
> backup plan.
> Use backup and restore to create the databases on the new system. Use the
> 'NORECOVERY' or 'STANDBY' option so you can apply later transaction logs.
> Manually copy and apply the transaction log backups from the old system to
> the new cluster.
> I suggest scripting the following tasks well ahead of time.
> Run a log backup WITH STANDBY on each database on the old server. Copy the
> files (or restore from a common network share) and restore the final log for
> each database using the WITH RECOVERY option.
> When you have transferred the final database log, use sp_change_users_login
> to remap your pre-generated logins to the users in the restored databases.
> I typically use a bogus password for SQL logins until this step so that
> users cannot accidentally connect to the new server.
> Stop the old server. Add the SVC record to DNS to alias the old servername
> to the new service. Remember to include the port number if you are using a
> named instance or a non-standard port.
> Get ready to deal with the handful of systems you missed that are still
> connecting via IP.
> Remember to test everything before going live. If you mess up, you can
> always bring the old server back up and take the databases out of standby to
> get back to where you started. The actual changeover should take less than
> one hour IF you plan, test, and practice.
> Good luck.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
> news:59B178D2-D730-4142-BE76-E0A38FE53F69@.microsoft.com...
> And
> done
>
>
sql
I have read most the articles and posts about move sql server.
Here is my situation:
I have stand alone standard sql server 2000 and with about 40 databases. And
I am moving the server to a SQL cluster(Active/passive). I have to use the
old name, IP on the new server and with minimum down time. Anybody has done
this? What is the precedure? Will Virutas BackupExe backup/restore work? I
know Deattach/Reattach works but I have to do it one DB at a time, right?
That will take a long time. Will permission be carried over using these
mothed?
Any information will be greatly appreciated.
Thanks,
Yuhong
First, you cannot use the same name and IP address. The cluster
installation and any data transfer will fail.
Here is how you do this.
First, make sure all your SQL connections to the old box use a DNS entry to
resolve their names. Eliminate any hard-coded IP addresses by using client
aliases if necessary. You will use an SVC record in the DNS system to
repoint the old connections to the new server when you do the changeover.
Test this using a bogus alias before going live.
Set all your production databases to full recovery and implement a log
backup plan.
Use backup and restore to create the databases on the new system. Use the
'NORECOVERY' or 'STANDBY' option so you can apply later transaction logs.
Manually copy and apply the transaction log backups from the old system to
the new cluster.
I suggest scripting the following tasks well ahead of time.
Run a log backup WITH STANDBY on each database on the old server. Copy the
files (or restore from a common network share) and restore the final log for
each database using the WITH RECOVERY option.
When you have transferred the final database log, use sp_change_users_login
to remap your pre-generated logins to the users in the restored databases.
I typically use a bogus password for SQL logins until this step so that
users cannot accidentally connect to the new server.
Stop the old server. Add the SVC record to DNS to alias the old servername
to the new service. Remember to include the port number if you are using a
named instance or a non-standard port.
Get ready to deal with the handful of systems you missed that are still
connecting via IP.
Remember to test everything before going live. If you mess up, you can
always bring the old server back up and take the databases out of standby to
get back to where you started. The actual changeover should take less than
one hour IF you plan, test, and practice.
Good luck.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
news:59B178D2-D730-4142-BE76-E0A38FE53F69@.microsoft.com...
> Hi
> I have read most the articles and posts about move sql server.
> Here is my situation:
> I have stand alone standard sql server 2000 and with about 40 databases.
And
> I am moving the server to a SQL cluster(Active/passive). I have to use the
> old name, IP on the new server and with minimum down time. Anybody has
done
> this? What is the precedure? Will Virutas BackupExe backup/restore work? I
> know Deattach/Reattach works but I have to do it one DB at a time, right?
> That will take a long time. Will permission be carried over using these
> mothed?
> Any information will be greatly appreciated.
> Thanks,
> --
> Yuhong
|||Thanks, Geoff! This is very helpful. I have setup a test cluster and I will
have to do a few full test before the real migration.
Thanks again!
Yuhong
"Geoff N. Hiten" wrote:
> First, you cannot use the same name and IP address. The cluster
> installation and any data transfer will fail.
> Here is how you do this.
> First, make sure all your SQL connections to the old box use a DNS entry to
> resolve their names. Eliminate any hard-coded IP addresses by using client
> aliases if necessary. You will use an SVC record in the DNS system to
> repoint the old connections to the new server when you do the changeover.
> Test this using a bogus alias before going live.
> Set all your production databases to full recovery and implement a log
> backup plan.
> Use backup and restore to create the databases on the new system. Use the
> 'NORECOVERY' or 'STANDBY' option so you can apply later transaction logs.
> Manually copy and apply the transaction log backups from the old system to
> the new cluster.
> I suggest scripting the following tasks well ahead of time.
> Run a log backup WITH STANDBY on each database on the old server. Copy the
> files (or restore from a common network share) and restore the final log for
> each database using the WITH RECOVERY option.
> When you have transferred the final database log, use sp_change_users_login
> to remap your pre-generated logins to the users in the restored databases.
> I typically use a bogus password for SQL logins until this step so that
> users cannot accidentally connect to the new server.
> Stop the old server. Add the SVC record to DNS to alias the old servername
> to the new service. Remember to include the port number if you are using a
> named instance or a non-standard port.
> Get ready to deal with the handful of systems you missed that are still
> connecting via IP.
> Remember to test everything before going live. If you mess up, you can
> always bring the old server back up and take the databases out of standby to
> get back to where you started. The actual changeover should take less than
> one hour IF you plan, test, and practice.
> Good luck.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
> news:59B178D2-D730-4142-BE76-E0A38FE53F69@.microsoft.com...
> And
> done
>
>
sql
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
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
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
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
Wednesday, March 21, 2012
Migrate from user instance to native db in SQL Server Express ?
Hello,
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/...&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically
I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB i
s
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>sql
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/...&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically
I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB i
s
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>sql
Migrate from user instance to native db in SQL Server Express ?
Hello,
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?
Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/details.aspx?FamilyID=fa87e828-173f-472e-a85c-27ed01cf6b02&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB is
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?
Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/details.aspx?FamilyID=fa87e828-173f-472e-a85c-27ed01cf6b02&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB is
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>
Migrate from user instance to native db in SQL Server Express ?
Hello,
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/details.aspx?FamilyID=fa87e828-173f-472e-a85c-27ed01cf6b02&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB is
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>
I am currently looking at migrating a database which has been running in
"user instance" mode, onto the standard sql server express mode. Basically I
need to be able to connect to the database while it's running from other
scripts and the management studio, which I cannot do nicely while the DB is
running in user mode.
Is there any tools or good instructions on doing this?
At this point I've re-created the database from scratch and imported data,
however I am looking for a cleaner/effective way of doing this. Any
suggestions?Hi
I am not a SQLExpress expert, ut SSEUTIL will allow you to attach to a user
instance of SQL Express.
http://www.microsoft.com/downloads/details.aspx?FamilyID=fa87e828-173f-472e-a85c-27ed01cf6b02&DisplayLang=en
You could then detach (sp_detach_db) the database and re-attach
(sp_attach_db) it to the main instance of SQL Server.
You would need to change the connection string in the application that
creates the user instance to reference the main instance of SQL Server and
not create the user instance.
John
"NSiggel" wrote:
> Hello,
> I am currently looking at migrating a database which has been running in
> "user instance" mode, onto the standard sql server express mode. Basically I
> need to be able to connect to the database while it's running from other
> scripts and the management studio, which I cannot do nicely while the DB is
> running in user mode.
> Is there any tools or good instructions on doing this?
> At this point I've re-created the database from scratch and imported data,
> however I am looking for a cleaner/effective way of doing this. Any
> suggestions?
>
Monday, March 12, 2012
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
Friday, February 24, 2012
Microsoft SQL Server, Error: 15314
When I try to connect to MS SQL Server 2005 standard edition it appear the error message as [Either no algorithm has been specified or the bitlength and the algorithm specified for the key are not available in this installation of windows (Microsoft SQL Server, Error: 15314)].
Please anyone explain me how this error message mean. How to solve this matter to avoid this happen anymore.
Thank you
Simba
If you are on windows 2000 then this is probably due to the existence of a symmetric key with the AES alogorithm.
Check the create symmetric key entry in Books Online and check the following topic: Choosing an Encryption Algorithm
HTH,
-Steven Gott
SDE/T
SQL Server
|||Thanks Steven for your reply.
I am using Window Advanced Server 2003. The error does not happen every time I login to the SQL Server 2005 but it just happens sometimes. I mean I have a website that connects to SQL Server. My users can use properly just sometimes they cannot connect to the database. So I have to try to connect directly to database and it appears the error.
Simba
|||Looks like a symmetric key issue as this is a one key that is used for both encryption and decryption. This is a fast, commonly used method for encryption. As with a certificate, many parameters are available when creating Symmetric Keys. In most cases, we only need a limited set of parameters. You can refer to Books Online for all the parameters.
Are you using any specific encryption algorithm?
Subscribe to:
Posts (Atom)