HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Friday, March 30, 2012
MSDE to SQL Server
HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
MSDE to SQL 2000
What's the best way to get the data from the MSDE server
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
MSDE to SQL 2000
What's the best way to get the data from the MSDE server
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
MSDE to SQL
When scaling a system's back end from MSDE to the enterprise version of SQL what types of issues or concerns would you watch for?
Thanks
I am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/pr...o/overview.asp
Greg Jackson
PDX, Oregon
|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
sql
Thanks
I am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/pr...o/overview.asp
Greg Jackson
PDX, Oregon
|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
sql
MSDE to SQL
When scaling a system's back end from MSDE to the enterprise version of SQL
what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/p...fo/overview.asp
Greg Jackson
PDX, Oregon|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/p...fo/overview.asp
Greg Jackson
PDX, Oregon|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
MSDE to SQL
When scaling a system's back end from MSDE to the enterprise version of SQL what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/productinfo/overview.asp
Greg Jackson
PDX, Oregon|||i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not se the SQL server.
My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the domain
"Jaxon" wrote:
> I am sure there are tons of white papers on this, but I dont suspect that
> you'll experience any huge hurdles.
> MSDE is essentially a throttled down version of the SQL Server Engine.
> "Because it is fully compatible with other editions of SQL Server,
> developers can easily target both SQL Server and MSDE 2000 with the same
> core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> Server if an application grows beyond the storage and scalability limits of
> MSDE 2000."
>
> http://www.microsoft.com/sql/msde/productinfo/overview.asp
>
>
> Greg Jackson
> PDX, Oregon
>
>|||MSDE doesn't have network access enabled by default. Enable using svrnetcn.exe.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Visual FoxPro programmer" <VisualFoxProprogrammer@.discussions.microsoft.com> wrote in message
news:927CFF5D-751E-4040-AF0D-B3896E64D68C@.microsoft.com...
> i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a
domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not
se the SQL server.
> My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the
domain
>
> "Jaxon" wrote:
> > I am sure there are tons of white papers on this, but I dont suspect that
> > you'll experience any huge hurdles.
> >
> > MSDE is essentially a throttled down version of the SQL Server Engine.
> >
> > "Because it is fully compatible with other editions of SQL Server,
> > developers can easily target both SQL Server and MSDE 2000 with the same
> > core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> > Server if an application grows beyond the storage and scalability limits of
> > MSDE 2000."
> >
> >
> > http://www.microsoft.com/sql/msde/productinfo/overview.asp
> >
> >
> >
> >
> > Greg Jackson
> > PDX, Oregon
> >
> >
> >|||Miles,
MSDE IS SQL Server... You should have no problems at all...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/productinfo/overview.asp
Greg Jackson
PDX, Oregon|||i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not se the SQL server.
My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the domain
"Jaxon" wrote:
> I am sure there are tons of white papers on this, but I dont suspect that
> you'll experience any huge hurdles.
> MSDE is essentially a throttled down version of the SQL Server Engine.
> "Because it is fully compatible with other editions of SQL Server,
> developers can easily target both SQL Server and MSDE 2000 with the same
> core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> Server if an application grows beyond the storage and scalability limits of
> MSDE 2000."
>
> http://www.microsoft.com/sql/msde/productinfo/overview.asp
>
>
> Greg Jackson
> PDX, Oregon
>
>|||MSDE doesn't have network access enabled by default. Enable using svrnetcn.exe.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Visual FoxPro programmer" <VisualFoxProprogrammer@.discussions.microsoft.com> wrote in message
news:927CFF5D-751E-4040-AF0D-B3896E64D68C@.microsoft.com...
> i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a
domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not
se the SQL server.
> My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the
domain
>
> "Jaxon" wrote:
> > I am sure there are tons of white papers on this, but I dont suspect that
> > you'll experience any huge hurdles.
> >
> > MSDE is essentially a throttled down version of the SQL Server Engine.
> >
> > "Because it is fully compatible with other editions of SQL Server,
> > developers can easily target both SQL Server and MSDE 2000 with the same
> > core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> > Server if an application grows beyond the storage and scalability limits of
> > MSDE 2000."
> >
> >
> > http://www.microsoft.com/sql/msde/productinfo/overview.asp
> >
> >
> >
> >
> > Greg Jackson
> > PDX, Oregon
> >
> >
> >|||Miles,
MSDE IS SQL Server... You should have no problems at all...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
Subscribe to:
Posts (Atom)