Difference between Standard and Enterprise Edition

Where can I find about differences between two edition. I need to advise thi
s
for a customer who would be quering over the WANHi
http://www.microsoft.com/sql/editio...rd/default.mspx
"Tariq" <Tariq@.discussions.microsoft.com> wrote in message
news:FF73CE26-9939-4621-83B9-67222E648CE9@.microsoft.com...
> Where can I find about differences between two edition. I need to advise
> this
> for a customer who would be quering over the WAN

Difference between Standard and Enterprise Edition

Where can I find about differences between two edition. I need to advise this
for a customer who would be quering over the WANHi
http://www.microsoft.com/sql/editions/standard/default.mspx
"Tariq" <Tariq@.discussions.microsoft.com> wrote in message
news:FF73CE26-9939-4621-83B9-67222E648CE9@.microsoft.com...
> Where can I find about differences between two edition. I need to advise
> this
> for a customer who would be quering over the WANsql

Difference between Standard and Enterprise Edition

Where can I find about differences between two edition. I need to advise this
for a customer who would be quering over the WAN
Hi
http://www.microsoft.com/sql/edition...d/default.mspx
"Tariq" <Tariq@.discussions.microsoft.com> wrote in message
news:FF73CE26-9939-4621-83B9-67222E648CE9@.microsoft.com...
> Where can I find about differences between two edition. I need to advise
> this
> for a customer who would be quering over the WAN

difference between SQL standard Edition and Enterprise Edition

Hi, there,

We are running SQL 2000 & SP4 with our ASP.NET application, now we plan to upgrade to Enterprise Edition due to the huge diffirence in price. Can any one of u give an brief introduction of the difference between these two, and what is the advantages of enterprise edition?

Any suggestion will greately appreciated.

Shermaine

There's a good comparison of the various versions of SQL Server here:-

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

|||

shermaine wrote:

now we plan to upgrade to Enterprise Edition due to the huge diffirence in price.

That seems logical.

difference between sql 2000 standard Edition and Enterprise Editio

Hi, there,
I hv a few question on SQL 2000 server: Currently we are runing SQL 2000
with SP4, now we want upgrade to SQL 2000 Enterprise Edition. ( We Don't want
to upgrade to 2005 Eterprise Edition immediately due to other reason), can
any one of u tell me the difference between standard Edition and Enterprise
Edition due to there is a huge difference in price.
Thanks in advanced
Rgds
ShermaineHi
A list of features is at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
The higher spec hardware support is at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
John
"xiaomei" wrote:
> Hi, there,
> I hv a few question on SQL 2000 server: Currently we are runing SQL 2000
> with SP4, now we want upgrade to SQL 2000 Enterprise Edition. ( We Don't want
> to upgrade to 2005 Eterprise Edition immediately due to other reason), can
> any one of u tell me the difference between standard Edition and Enterprise
> Edition due to there is a huge difference in price.
> Thanks in advanced
> Rgds
> Shermaine|||Also know that if you are running Windows XP you cannot install enterprise
edition
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1|||Dear John,
Thanks so much.
Have a nice day!
Shermaine
"John Bell" wrote:
> Hi
> A list of features is at:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_1cdv.asp
> The higher spec hardware support is at:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
> John
>
> "xiaomei" wrote:
> > Hi, there,
> > I hv a few question on SQL 2000 server: Currently we are runing SQL 2000
> > with SP4, now we want upgrade to SQL 2000 Enterprise Edition. ( We Don't want
> > to upgrade to 2005 Eterprise Edition immediately due to other reason), can
> > any one of u tell me the difference between standard Edition and Enterprise
> > Edition due to there is a huge difference in price.
> >
> > Thanks in advanced
> >
> > Rgds
> > Shermaine|||Hi, thanks a lot.
Yes, we will run on windows 2000 server.
BTW, Does Microsoft still provide evaluation copy download for Windows SQL
2000 Enterprise Edition?
Thanks
Shermaine
"Prospero via SQLMonster.com" wrote:
> Also know that if you are running Windows XP you cannot install enterprise
> edition
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1
>|||Hi
An evaluation copy would only be needed if you are going to use the
additional features. I would not load this into a live environment. An
alternative might be to use the developer edition in your test environment,
if this is for stress testing then you should use similar hardware to the
live environment.
John
"xiaomei" wrote:
> Hi, thanks a lot.
> Yes, we will run on windows 2000 server.
> BTW, Does Microsoft still provide evaluation copy download for Windows SQL
> 2000 Enterprise Edition?
> Thanks
> Shermaine
> "Prospero via SQLMonster.com" wrote:
> > Also know that if you are running Windows XP you cannot install enterprise
> > edition
> >
> > --
> > Message posted via SQLMonster.com
> > http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200601/1
> >

difference between sql 2000 standard Edition and Enterprise Editio

Hi, there,
I hv a few question on SQL 2000 server: Currently we are runing SQL 2000
with SP4, now we want upgrade to SQL 2000 Enterprise Edition. ( We Don't wan
t
to upgrade to 2005 Eterprise Edition immediately due to other reason), can
any one of u tell me the difference between standard Edition and Enterprise
Edition due to there is a huge difference in price.
Thanks in advanced
Rgds
ShermaineHi
A list of features is at:
http://msdn.microsoft.com/library/d...br />
1cdv.asp
The higher spec hardware support is at:
http://msdn.microsoft.com/library/d...br />
8dbn.asp
John
"xiaomei" wrote:

> Hi, there,
> I hv a few question on SQL 2000 server: Currently we are runing SQL 2000
> with SP4, now we want upgrade to SQL 2000 Enterprise Edition. ( We Don't w
ant
> to upgrade to 2005 Eterprise Edition immediately due to other reason), can
> any one of u tell me the difference between standard Edition and Enterpris
e
> Edition due to there is a huge difference in price.
> Thanks in advanced
> Rgds
> Shermaine|||Also know that if you are running Windows XP you cannot install enterprise
edition
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200601/1

difference between sql 2000 standard Edition and Enterprise Editio

Hi, there,
I hv a few question on SQL 2000 server: Currently we are runing SQL 2000
with SP4, now we want upgrade to SQL 2000 Enterprise Edition. ( We Don't want
to upgrade to 2005 Eterprise Edition immediately due to other reason), can
any one of u tell me the difference between standard Edition and Enterprise
Edition due to there is a huge difference in price.
Thanks in advanced
Rgds
Shermaine
Hi
A list of features is at:
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
The higher spec hardware support is at:
http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
John
"xiaomei" wrote:

> Hi, there,
> I hv a few question on SQL 2000 server: Currently we are runing SQL 2000
> with SP4, now we want upgrade to SQL 2000 Enterprise Edition. ( We Don't want
> to upgrade to 2005 Eterprise Edition immediately due to other reason), can
> any one of u tell me the difference between standard Edition and Enterprise
> Edition due to there is a huge difference in price.
> Thanks in advanced
> Rgds
> Shermaine
|||Also know that if you are running Windows XP you cannot install enterprise
edition
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200601/1

Difference between Personal Edition and Standard Edition

We had a vendor install SQL Server Personal Edition
instead of the Standard Edition on one of our servers.
When we asked them "what is the difference" they did not
know. Can someone tell me what it is? We paid for the
Standard (FULL) install..Refer to this url
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_ts_1cdv.asp
--
-Vishal
"Ed" <fsankey@.hotmail.com> wrote in message
news:00a501c3634f$9fba9fc0$a401280a@.phx.gbl...
> We had a vendor install SQL Server Personal Edition
> instead of the Standard Edition on one of our servers.
> When we asked them "what is the difference" they did not
> know. Can someone tell me what it is? We paid for the
> Standard (FULL) install..

Did it really successfully install?

SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed =
SQL Server 7 on the server and although the installer ended successfully =
I have this in the sqlstp.log:
20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sqldbreg.exe -RegServer
20:44:13 Process Exit Code: (-2147312566) Error loading type =
library/DLL.
....
20:44:16 Installation Succeeded
Should I fix this and if so how? Thanks.
I looked to see if I have the file sqldbreg.exe and I do. It is in =
Microsoft Visual Studio 6\Common\...
--=20
George Hester
_________________________________
This sounds like the installer had an issue registring the sql debuger
utility integrated with your Visual Studio instalation. This should affect
the SQL Server installation but might keep you from properly using the
debuging tools.
I would service pack your SS7 installation and then service pack your VS
installations.
Sincerely,
Anthony Thomas

"George Hester" <hesterloli@.hotmail.com> wrote in message
news:Oqunpls8EHA.1084@.TK2MSFTNGP15.phx.gbl...
SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed SQL
Server 7 on the server and although the installer ended successfully I have
this in the sqlstp.log:
20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sqldbreg.exe -RegServer
20:44:13 Process Exit Code: (-2147312566) Error loading type library/DLL.
....
20:44:16 Installation Succeeded
Should I fix this and if so how? Thanks.
I looked to see if I have the file sqldbreg.exe and I do. It is in
Microsoft Visual Studio 6\Common\...
George Hester
_________________________________
|||Yes that is what it was. It turned out DCOM settings and file locations =
were not set right. I manually fixed it. Thanks.
--=20
George Hester
_________________________________
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message =
news:etAJppIDFHA.3132@.TK2MSFTNGP09.phx.gbl...
> This sounds like the installer had an issue registring the sql debuger
> utility integrated with your Visual Studio instalation. This should =
affect
> the SQL Server installation but might keep you from properly using the
> debuging tools.
>=20
> I would service pack your SS7 installation and then service pack your =
VS
> installations.
>=20
> Sincerely,
>=20
>=20
> Anthony Thomas
>=20
>=20
> --=20
>=20
> "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:Oqunpls8EHA.1084@.TK2MSFTNGP15.phx.gbl...
> SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed =
SQL
> Server 7 on the server and although the installer ended successfully I =
have
> this in the sqlstp.log:
>=20
> 20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sqldbreg.exe =
-RegServer
> 20:44:13 Process Exit Code: (-2147312566) Error loading type =
library/DLL.
> ...
> 20:44:16 Installation Succeeded
>=20
> Should I fix this and if so how? Thanks.
>=20
> I looked to see if I have the file sqldbreg.exe and I do. It is in
> Microsoft Visual Studio 6\Common\...
>=20
> --=20
> George Hester
> _________________________________
>=20
>=20

Did it really successfully install?

SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed = SQL Server 7 on the server and although the installer ended successfully = I have this in the sqlstp.log:
20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sqldbreg.exe -RegServer
20:44:13 Process Exit Code: (-2147312566) Error loading type = library/DLL.
...
20:44:16 Installation Succeeded
Should I fix this and if so how? Thanks.
I looked to see if I have the file sqldbreg.exe and I do. It is in = Microsoft Visual Studio 6\Common\...
-- George Hester
_________________________________This sounds like the installer had an issue registring the sql debuger
utility integrated with your Visual Studio instalation. This should affect
the SQL Server installation but might keep you from properly using the
debuging tools.
I would service pack your SS7 installation and then service pack your VS
installations.
Sincerely,
Anthony Thomas
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:Oqunpls8EHA.1084@.TK2MSFTNGP15.phx.gbl...
SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed SQL
Server 7 on the server and although the installer ended successfully I have
this in the sqlstp.log:
20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sqldbreg.exe -RegServer
20:44:13 Process Exit Code: (-2147312566) Error loading type library/DLL.
...
20:44:16 Installation Succeeded
Should I fix this and if so how? Thanks.
I looked to see if I have the file sqldbreg.exe and I do. It is in
Microsoft Visual Studio 6\Common\...
--
George Hester
_________________________________|||Yes that is what it was. It turned out DCOM settings and file locations =were not set right. I manually fixed it. Thanks.
-- George Hester
_________________________________
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message =news:etAJppIDFHA.3132@.TK2MSFTNGP09.phx.gbl...
> This sounds like the installer had an issue registring the sql debuger
> utility integrated with your Visual Studio instalation. This should =affect
> the SQL Server installation but might keep you from properly using the
> debuging tools.
> > I would service pack your SS7 installation and then service pack your =VS
> installations.
> > Sincerely,
> > > Anthony Thomas
> > > -- > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:Oqunpls8EHA.1084@.TK2MSFTNGP15.phx.gbl...
> SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed =SQL
> Server 7 on the server and although the installer ended successfully I =have
> this in the sqlstp.log:
> > 20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sqldbreg.exe =-RegServer
> 20:44:13 Process Exit Code: (-2147312566) Error loading type =library/DLL.
> ...
> 20:44:16 Installation Succeeded
> > Should I fix this and if so how? Thanks.
> > I looked to see if I have the file sqldbreg.exe and I do. It is in
> Microsoft Visual Studio 6\Common\...
> > -- > George Hester
> _________________________________
> >=20

Did it really successfully install?

SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed =
SQL Server 7 on the server and although the installer ended successfully =
I have this in the sqlstp.log:
20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sq
ldbreg.exe -RegServer
20:44:13 Process Exit Code: (-2147312566) Error loading type =
library/DLL.
...
20:44:16 Installation Succeeded
Should I fix this and if so how? Thanks.
I looked to see if I have the file sqldbreg.exe and I do. It is in =
Microsoft Visual Studio 6\Common\...
--=20
George Hester
_________________________________This sounds like the installer had an issue registring the sql debuger
utility integrated with your Visual Studio instalation. This should affect
the SQL Server installation but might keep you from properly using the
debuging tools.
I would service pack your SS7 installation and then service pack your VS
installations.
Sincerely,
Anthony Thomas
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:Oqunpls8EHA.1084@.TK2MSFTNGP15.phx.gbl...
SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed SQL
Server 7 on the server and although the installer ended successfully I have
this in the sqlstp.log:
20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sq
ldbreg.exe -RegServer
20:44:13 Process Exit Code: (-2147312566) Error loading type library/DLL.
...
20:44:16 Installation Succeeded
Should I fix this and if so how? Thanks.
I looked to see if I have the file sqldbreg.exe and I do. It is in
Microsoft Visual Studio 6\Common\...
George Hester
_________________________________|||Yes that is what it was. It turned out DCOM settings and file locations =
were not set right. I manually fixed it. Thanks.
--=20
George Hester
_________________________________
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message =
news:etAJppIDFHA.3132@.TK2MSFTNGP09.phx.gbl...
> This sounds like the installer had an issue registring the sql debuger
> utility integrated with your Visual Studio instalation. This should =
affect
> the SQL Server installation but might keep you from properly using the
> debuging tools.
>=20
> I would service pack your SS7 installation and then service pack your =
VS
> installations.
>=20
> Sincerely,
>=20
>=20
> Anthony Thomas
>=20
>=20
> --=20
>=20
> "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:Oqunpls8EHA.1084@.TK2MSFTNGP15.phx.gbl...
> SQL 7 Standard on Windows 2000 Advanced Server SP2. I just installed =
SQL
> Server 7 on the server and although the installer ended successfully I =
have
> this in the sqlstp.log:
>=20
> 20:44:13 C:\PROGRA~1\MICROS~3\Common\IDE\IDE98\sq
ldbreg.exe =
-RegServer
> 20:44:13 Process Exit Code: (-2147312566) Error loading type =
library/DLL.
> ...
> 20:44:16 Installation Succeeded
>=20
> Should I fix this and if so how? Thanks.
>=20
> I looked to see if I have the file sqldbreg.exe and I do. It is in
> Microsoft Visual Studio 6\Common\...
>=20
> --=20
> George Hester
> _________________________________
>=20
>=20

Developing CLR Objects - Visual Studio Requirements?

I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
on either system's VS installation the option to create a new Sql
Project/Solution to create CLR objects. Am I missing something, or do I
need VS Professional?
CraigHi Craig,
the option should be under
FIle --> New --> Project --> (Programming Language, e.g. C# ) -->
Database --> SQLServer project
In the Project you can define new object types like functions /
procedures / UDA etc.
HTH, Jens Suessmeyer.|||AFAIK, you need VS Professional version or (beta of) Team System dev.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/bobb
"Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
>and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
>on either system's VS installation the option to create a new Sql
>Project/Solution to create CLR objects. Am I missing something, or do I
>need VS Professional?
> Craig
>|||You don't need to use Visual Studio to create and run
assemblies in SQL Server:
http://www.eggheadcafe.com/articles...5_clr_regex.asp
Robbe Morris - 2004/2005 Microsoft MVP C#
http://www.eggheadcafe.com/forums/merit.asp
"Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>I have SQL 2005 Express & Visual Studio 2005 Standard on my XP workstation,
>and SQL 2005 Standard installed on my Win2k3 server. I can't find anywhere
>on either system's VS installation the option to create a new Sql
>Project/Solution to create CLR objects. Am I missing something, or do I
>need VS Professional?
> Craig
>|||True. By the description in the posting, it appeared that he was looking for
the built-in Visual Studio "SQL Server Projects" for .NET languages, that
are included as part of some editions of Visual Studio.
You could conceivably develop and deploy SQLCLR assemblies with a command
line compiler and SQLCMD.exe.
Cheers,
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"Robbe Morris [C# MVP]" <info@.eggheadcafe.com> wrote in message
news:%23XoVWSLDGHA.3984@.TK2MSFTNGP14.phx.gbl...
> You don't need to use Visual Studio to create and run
> assemblies in SQL Server:
> http://www.eggheadcafe.com/articles...5_clr_regex.asp
> --
> Robbe Morris - 2004/2005 Microsoft MVP C#
> http://www.eggheadcafe.com/forums/merit.asp
>
>
> "Craig S" <cscheets@.dontspam.kc.rr.com> wrote in message
> news:e$AATwKDGHA.1384@.TK2MSFTNGP11.phx.gbl...
>|||Niels Berglund has released an custom SQL Server project, VS addin and a
stand-alone SQL CLR deployment tool which work with any edition of Visual
Studio.
http://staff.develop.com/nielsb/cod...ropAndAddIn.zip
David
"Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
news:%23AIOLzMDGHA.628@.TK2MSFTNGP14.phx.gbl...
> True. By the description in the posting, it appeared that he was looking
> for the built-in Visual Studio "SQL Server Projects" for .NET languages,
> that are included as part of some editions of Visual Studio.
> You could conceivably develop and deploy SQLCLR assemblies with a command
> line compiler and SQLCMD.exe.
> Cheers,
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb
>
> "Robbe Morris [C# MVP]" <info@.eggheadcafe.com> wrote in message
> news:%23XoVWSLDGHA.3984@.TK2MSFTNGP14.phx.gbl...
>|||Yep. I was aware of that too. ;-) It sounded as though the questioner was
asking/wondering why the built-in projects didn't show up, rather than what
are the choices when...
Bob Beauchemin
http://www.SQLskills.com/blogs/bobb
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:eYUIWFNDGHA.748@.TK2MSFTNGP12.phx.gbl...
> Niels Berglund has released an custom SQL Server project, VS addin and a
> stand-alone SQL CLR deployment tool which work with any edition of Visual
> Studio.
> http://staff.develop.com/nielsb/cod...ropAndAddIn.zip
> David
>
> "Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
> news:%23AIOLzMDGHA.628@.TK2MSFTNGP14.phx.gbl...
>|||I was kind of asking both, mainly "how do I develop one without notepad.exe"
:) I found all of these posts to be both correct and very helpful, thank
you all.
Craig
"Bob Beauchemin" <no_bobb_spam@.sqlskills.com> wrote in message
news:uCuImBODGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Yep. I was aware of that too. ;-) It sounded as though the questioner was
> asking/wondering why the built-in projects didn't show up, rather than
> what are the choices when...
> Bob Beauchemin
> http://www.SQLskills.com/blogs/bobb
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:eYUIWFNDGHA.748@.TK2MSFTNGP12.phx.gbl...
>

Developer to Standard

We just finished development of a set of databases with Dev Edition and want
to move them into production. We'd like to use the same machine for the
production databases. We'd also like to uninstall Dev Edition and install
Standard.
What is the best way to move all of the databases from the old (Dev)
instance to the new (Standard) instance. We're not using any of the
'features' unique to Dev/Enterprise. Pretty basic stuff.
Thanks.
Mike Murphy
I would do a sp_detach_db to unattach your database (or you can do the same
for Enterprise Manager). Uninstall dev. Install Standard. Then do an
sp_attach_db (or the same from Enterprise Manager) to attach your database
files back to SQL Server.
"Mike Murphy" wrote:

> We just finished development of a set of databases with Dev Edition and want
> to move them into production. We'd like to use the same machine for the
> production databases. We'd also like to uninstall Dev Edition and install
> Standard.
> What is the best way to move all of the databases from the old (Dev)
> instance to the new (Standard) instance. We're not using any of the
> 'features' unique to Dev/Enterprise. Pretty basic stuff.
> Thanks.
> --
> Mike Murphy
|||Before you do anything to your configuration, get a good backup. Then you
can uninstall Dev, install standard and either restore from backup or
sp_attachdb to re-attach your database files.
But get that backup first.
"Mike Murphy" <MikeMurphy@.discussions.microsoft.com> wrote in message
news:9AD45589-7D05-4B5A-88BB-DE850C577F94@.microsoft.com...
> We just finished development of a set of databases with Dev Edition and
> want
> to move them into production. We'd like to use the same machine for the
> production databases. We'd also like to uninstall Dev Edition and install
> Standard.
> What is the best way to move all of the databases from the old (Dev)
> instance to the new (Standard) instance. We're not using any of the
> 'features' unique to Dev/Enterprise. Pretty basic stuff.
> Thanks.
> --
> Mike Murphy
|||Won't you want both development and live environments once you go into
production?
One point in addition to the other responses. Dev Ed is equivalent to
Enterprise Ed not Standard. As the feature set is slightly different I
suggest you test on a Standard Ed installation before you go into
production. Of course that should happen anyway. Never test only in the Dev
environment.
David Portas
SQL Server MVP

Developer to Standard

We just finished development of a set of databases with Dev Edition and want
to move them into production. We'd like to use the same machine for the
production databases. We'd also like to uninstall Dev Edition and install
Standard.
What is the best way to move all of the databases from the old (Dev)
instance to the new (Standard) instance. We're not using any of the
'features' unique to Dev/Enterprise. Pretty basic stuff.
Thanks.
--
Mike MurphyI would do a sp_detach_db to unattach your database (or you can do the same
for Enterprise Manager). Uninstall dev. Install Standard. Then do an
sp_attach_db (or the same from Enterprise Manager) to attach your database
files back to SQL Server.
"Mike Murphy" wrote:
> We just finished development of a set of databases with Dev Edition and want
> to move them into production. We'd like to use the same machine for the
> production databases. We'd also like to uninstall Dev Edition and install
> Standard.
> What is the best way to move all of the databases from the old (Dev)
> instance to the new (Standard) instance. We're not using any of the
> 'features' unique to Dev/Enterprise. Pretty basic stuff.
> Thanks.
> --
> Mike Murphy|||Before you do anything to your configuration, get a good backup. Then you
can uninstall Dev, install standard and either restore from backup or
sp_attachdb to re-attach your database files.
But get that backup first.
"Mike Murphy" <MikeMurphy@.discussions.microsoft.com> wrote in message
news:9AD45589-7D05-4B5A-88BB-DE850C577F94@.microsoft.com...
> We just finished development of a set of databases with Dev Edition and
> want
> to move them into production. We'd like to use the same machine for the
> production databases. We'd also like to uninstall Dev Edition and install
> Standard.
> What is the best way to move all of the databases from the old (Dev)
> instance to the new (Standard) instance. We're not using any of the
> 'features' unique to Dev/Enterprise. Pretty basic stuff.
> Thanks.
> --
> Mike Murphy|||Won't you want both development and live environments once you go into
production?
One point in addition to the other responses. Dev Ed is equivalent to
Enterprise Ed not Standard. As the feature set is slightly different I
suggest you test on a Standard Ed installation before you go into
production. Of course that should happen anyway. Never test only in the Dev
environment.
--
David Portas
SQL Server MVP
--

Developer to Standard

We just finished development of a set of databases with Dev Edition and want
to move them into production. We'd like to use the same machine for the
production databases. We'd also like to uninstall Dev Edition and install
Standard.
What is the best way to move all of the databases from the old (Dev)
instance to the new (Standard) instance. We're not using any of the
'features' unique to Dev/Enterprise. Pretty basic stuff.
Thanks.
--
Mike MurphyI would do a sp_detach_db to unattach your database (or you can do the same
for Enterprise Manager). Uninstall dev. Install Standard. Then do an
sp_attach_db (or the same from Enterprise Manager) to attach your database
files back to SQL Server.
"Mike Murphy" wrote:

> We just finished development of a set of databases with Dev Edition and wa
nt
> to move them into production. We'd like to use the same machine for the
> production databases. We'd also like to uninstall Dev Edition and install
> Standard.
> What is the best way to move all of the databases from the old (Dev)
> instance to the new (Standard) instance. We're not using any of the
> 'features' unique to Dev/Enterprise. Pretty basic stuff.
> Thanks.
> --
> Mike Murphy|||Before you do anything to your configuration, get a good backup. Then you
can uninstall Dev, install standard and either restore from backup or
sp_attachdb to re-attach your database files.
But get that backup first.
"Mike Murphy" <MikeMurphy@.discussions.microsoft.com> wrote in message
news:9AD45589-7D05-4B5A-88BB-DE850C577F94@.microsoft.com...
> We just finished development of a set of databases with Dev Edition and
> want
> to move them into production. We'd like to use the same machine for the
> production databases. We'd also like to uninstall Dev Edition and install
> Standard.
> What is the best way to move all of the databases from the old (Dev)
> instance to the new (Standard) instance. We're not using any of the
> 'features' unique to Dev/Enterprise. Pretty basic stuff.
> Thanks.
> --
> Mike Murphy|||Won't you want both development and live environments once you go into
production?
One point in addition to the other responses. Dev Ed is equivalent to
Enterprise Ed not Standard. As the feature set is slightly different I
suggest you test on a Standard Ed installation before you go into
production. Of course that should happen anyway. Never test only in the Dev
environment.
David Portas
SQL Server MVP
--

developer edition vs standard edition

I have an application that a client would like to review.
They have the developer edition of SQL and would like to
try my app before buying the standard edition. Is there
anything they would not be able to do. I have a db that I
will attach with demo data, there are stored procedures,
views, etc.
Thanks in advanceThe Developer edition has the same functionality of the Enterprise =edition, so it can do everything that the Standard edition can do.
-- Keith
"max" <mshaneyfelt@.ciomsult.com> wrote in message =news:00fc01c3d3c5$b4915fb0$a501280a@.phx.gbl...
> I have an application that a client would like to review. > They have the developer edition of SQL and would like to > try my app before buying the standard edition. Is there > anything they would not be able to do. I have a db that I > will attach with demo data, there are stored procedures, > views, etc.
> > Thanks in advance|||In addition to Keith's comment, Dev Edition is meant for development
purposes only. You should not be using it for production.
http://www.microsoft.com/sql/howtobuy/development.asp
--
-oj
http://www.rac4sql.net
"max" <mshaneyfelt@.ciomsult.com> wrote in message
news:00fc01c3d3c5$b4915fb0$a501280a@.phx.gbl...
> I have an application that a client would like to review.
> They have the developer edition of SQL and would like to
> try my app before buying the standard edition. Is there
> anything they would not be able to do. I have a db that I
> will attach with demo data, there are stored procedures,
> views, etc.
> Thanks in advance|||oj, thanks. The client will not use it for production but
they already own the developer edition so this way they
can look at the application before laying out the funds
for a processor license.
>--Original Message--
>In addition to Keith's comment, Dev Edition is meant for
development
>purposes only. You should not be using it for production.
>http://www.microsoft.com/sql/howtobuy/development.asp
>--
>-oj
>http://www.rac4sql.net
>
>"max" <mshaneyfelt@.ciomsult.com> wrote in message
>news:00fc01c3d3c5$b4915fb0$a501280a@.phx.gbl...
>> I have an application that a client would like to
review.
>> They have the developer edition of SQL and would like to
>> try my app before buying the standard edition. Is there
>> anything they would not be able to do. I have a db that
I
>> will attach with demo data, there are stored procedures,
>> views, etc.
>> Thanks in advance
>
>.
>

Developer Edition to Standard Edition (SQL SERVER 2000)

I Need to migrate from SQL SERVER 2000 Developer Edition to Standard
Edition.
I install the Standard Edition CD, but it was so fast. (I use the replace
option) I didn't see the normal installation process... copying, etc.
It is ok doing that way?
In my Developer Edition, I had the SP3a, now... after installing the
Standard Edition it still is SP3.
Did I do the right way?
Any suggestions?
Any ideas?
Thanks in advance.
Look here:
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
You should refer to the version above 760. if you have this, you can be
quite sure that you applied SP3a or above :-)
HTH, Jens Suessmeyer.

Developer Edition to Standard Edition (SQL SERVER 2000)

I Need to migrate from SQL SERVER 2000 Developer Edition to Standard
Edition.
I install the Standard Edition CD, but it was so fast. (I use the replace
option) I didn't see the normal installation process... copying, etc.
It is ok doing that way?
In my Developer Edition, I had the SP3a, now... after installing the
Standard Edition it still is SP3.
Did I do the right way?
Any suggestions?
Any ideas?
Thanks in advance.Look here:
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
You should refer to the version above 760. if you have this, you can be
quite sure that you applied SP3a or above :-)
HTH, Jens Suessmeyer.

Developer Edition to Standard Edition (SQL SERVER 2000)

I Need to migrate from SQL SERVER 2000 Developer Edition to Standard
Edition.
I install the Standard Edition CD, but it was so fast. (I use the replace
option) I didn't see the normal installation process... copying, etc.
It is ok doing that way?
In my Developer Edition, I had the SP3a, now... after installing the
Standard Edition it still is SP3.
Did I do the right way?
Any suggestions?
Any ideas?
Thanks in advance.Look here:
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
You should refer to the version above 760. if you have this, you can be
quite sure that you applied SP3a or above :-)
HTH, Jens Suessmeyer.

Developer Edition and Standard Edition on the same machine

Hi All,
I have installed the Developer Edition on my computer and have been using
this SQL database for my project.
The SQL server Standard Edition is installed on the server and I need a SQL
client to be installed on my PC to be able to communicate with the SQL Serve
r
on the server. This would be for another project. When once the SQL client i
s
installed on my PC, will I still be able use the Developer Edition on the
local mahine as before, for the first project?
Thanks
kdPlease don't post independently in separate newsgroups. You can add
multiple newsgroups to the header and then all the answers appear as one.
See my reply in the other newsgroup.
Andrew J. Kelly SQL MVP
"kd" <kd@.discussions.microsoft.com> wrote in message
news:67B0C0CA-0413-4E73-8BA6-F6693BFEFC72@.microsoft.com...
> Hi All,
> I have installed the Developer Edition on my computer and have been using
> this SQL database for my project.
> The SQL server Standard Edition is installed on the server and I need a
> SQL
> client to be installed on my PC to be able to communicate with the SQL
> Server
> on the server. This would be for another project. When once the SQL client
> is
> installed on my PC, will I still be able use the Developer Edition on the
> local mahine as before, for the first project?
> Thanks
> kd|||Hi,
Thanks for the answer and sorry about that; didn't know that multiple
newsgroups could be added in the header.
Regards,
kd
"Andrew J. Kelly" wrote:

> Please don't post independently in separate newsgroups. You can add
> multiple newsgroups to the header and then all the answers appear as one.
> See my reply in the other newsgroup.
>
> --
> Andrew J. Kelly SQL MVP
>
> "kd" <kd@.discussions.microsoft.com> wrote in message
> news:67B0C0CA-0413-4E73-8BA6-F6693BFEFC72@.microsoft.com...
>
>