Question regarding backup of 2005 database to 2000.

I know it's not possible to backup a database in SQL2005, and restore to 2000. But, I've been asked if there are any 3rd party tools which can do this - such as SQL Litespeed - but I can't see anything regarding this on their website.

Does anyone know if litespeed or Redgate SQL Backup can restore to 2000 from 2005 ?

Thanks in advance,

Hi

You can do the following:

1. In SQL Management studio, generate the database script, you can specify that script be generated for SQL 2000.

2. Create the database and tables using the script.

3. DTS or SSIS the data from SQL 2005 tables to SQL 2000 tables.

4. Create the table contraints like indexes and foreign keys using the script generated in step 1.

5. Create rest of the objects.

hope that helps.

Jag

|||No. Every tool I have seen does a TSQL "BACKUP DATABASE" command to their own virtual file/drive.

The structure has changed and views, etc which are not compatible with 2000. There is no way to "backup" a 2005 and restore to 2000.

As mentioned you can create a script and output all the data and import it back into 2000.

Question on SQL Server 2000 installation

I am trying to install on SQL Server 2000 on Windows server 2003, web
edition. When I click on autorun, then choose server tools and components and
choose Install Server, nothing happens.
I was wondering if it possible to install SQL Server 2000 on Windows Server
2003 web edition. Is this a compatibility issue?
Thank you.
Vamshee
Windows Server 2003 Web Server Edition will not allow you to install SQL
Server 2000. It is not a licensed configuration.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> I am trying to install on SQL Server 2000 on Windows server 2003, web
> edition. When I click on autorun, then choose server tools and components
and
> choose Install Server, nothing happens.
> I was wondering if it possible to install SQL Server 2000 on Windows
Server
> 2003 web edition. Is this a compatibility issue?
> Thank you.
> Vamshee
|||Hi,
Organizations cannot use Windows Server 2003, Web Edition, to deploy
Microsoft SQL Server.
See the below link (Limitations paragraph):-
http://www.microsoft.com/windowsserv...rview/web.mspx
Thanks
Hari
SQL Server MVP
"Geoff N. Hiten" wrote:

> Windows Server 2003 Web Server Edition will not allow you to install SQL
> Server 2000. It is not a licensed configuration.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
> news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> and
> Server
>
>
|||Thanks for the information.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Organizations cannot use Windows Server 2003, Web Edition, to deploy
> Microsoft SQL Server.
> See the below link (Limitations paragraph):-
> http://www.microsoft.com/windowsserv...rview/web.mspx
> Thanks
> Hari
> SQL Server MVP
>
> "Geoff N. Hiten" wrote:

Question on SQL Server 2000 installation

I am trying to install on SQL Server 2000 on Windows server 2003, web
edition. When I click on autorun, then choose server tools and components an
d
choose Install Server, nothing happens.
I was wondering if it possible to install SQL Server 2000 on Windows Server
2003 web edition. Is this a compatibility issue'
Thank you.
VamsheeWindows Server 2003 Web Server Edition will not allow you to install SQL
Server 2000. It is not a licensed configuration.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> I am trying to install on SQL Server 2000 on Windows server 2003, web
> edition. When I click on autorun, then choose server tools and components
and
> choose Install Server, nothing happens.
> I was wondering if it possible to install SQL Server 2000 on Windows
Server
> 2003 web edition. Is this a compatibility issue'
> Thank you.
> Vamshee|||Hi,
Organizations cannot use Windows Server 2003, Web Edition, to deploy
Microsoft SQL Server.
See the below link (Limitations paragraph):-
http://www.microsoft.com/windowsser...erview/web.mspx
Thanks
Hari
SQL Server MVP
"Geoff N. Hiten" wrote:

> Windows Server 2003 Web Server Edition will not allow you to install SQL
> Server 2000. It is not a licensed configuration.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
> news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> and
> Server
>
>|||Thanks for the information.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Organizations cannot use Windows Server 2003, Web Edition, to deploy
> Microsoft SQL Server.
> See the below link (Limitations paragraph):-
> http://www.microsoft.com/windowsser...erview/web.mspx
> Thanks
> Hari
> SQL Server MVP
>
> "Geoff N. Hiten" wrote:
>

Question on SQL Server 2000 installation

I am trying to install on SQL Server 2000 on Windows server 2003, web
edition. When I click on autorun, then choose server tools and components and
choose Install Server, nothing happens.
I was wondering if it possible to install SQL Server 2000 on Windows Server
2003 web edition. Is this a compatibility issue'
Thank you.
VamsheeWindows Server 2003 Web Server Edition will not allow you to install SQL
Server 2000. It is not a licensed configuration.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> I am trying to install on SQL Server 2000 on Windows server 2003, web
> edition. When I click on autorun, then choose server tools and components
and
> choose Install Server, nothing happens.
> I was wondering if it possible to install SQL Server 2000 on Windows
Server
> 2003 web edition. Is this a compatibility issue'
> Thank you.
> Vamshee|||Hi,
Organizations cannot use Windows Server 2003, Web Edition, to deploy
Microsoft SQL Server.
See the below link (Limitations paragraph):-
http://www.microsoft.com/windowsserver2003/evaluation/overview/web.mspx
Thanks
Hari
SQL Server MVP
"Geoff N. Hiten" wrote:
> Windows Server 2003 Web Server Edition will not allow you to install SQL
> Server 2000. It is not a licensed configuration.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
> news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> > I am trying to install on SQL Server 2000 on Windows server 2003, web
> > edition. When I click on autorun, then choose server tools and components
> and
> > choose Install Server, nothing happens.
> >
> > I was wondering if it possible to install SQL Server 2000 on Windows
> Server
> > 2003 web edition. Is this a compatibility issue'
> >
> > Thank you.
> > Vamshee
>
>|||Thanks for the information.
"Hari Prasad" wrote:
> Hi,
> Organizations cannot use Windows Server 2003, Web Edition, to deploy
> Microsoft SQL Server.
> See the below link (Limitations paragraph):-
> http://www.microsoft.com/windowsserver2003/evaluation/overview/web.mspx
> Thanks
> Hari
> SQL Server MVP
>
> "Geoff N. Hiten" wrote:
> > Windows Server 2003 Web Server Edition will not allow you to install SQL
> > Server 2000. It is not a licensed configuration.
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "Vamshee" <Vamshee@.discussions.microsoft.com> wrote in message
> > news:56A57D60-720F-4512-AA27-53045E73DD7C@.microsoft.com...
> > > I am trying to install on SQL Server 2000 on Windows server 2003, web
> > > edition. When I click on autorun, then choose server tools and components
> > and
> > > choose Install Server, nothing happens.
> > >
> > > I was wondering if it possible to install SQL Server 2000 on Windows
> > Server
> > > 2003 web edition. Is this a compatibility issue'
> > >
> > > Thank you.
> > > Vamshee
> >
> >
> >sql

Question on DEveloper EDition Client Tools Only

Hi:
Our developer's are supposed to use SQL Server Developer Edition Client
Tools Only.
Can anybody tell me if any of the components below could be considered
as that tool?
Many thanks in advance.
Analysis Services Shared Tools
=B7 Business Intelligence Development Studio
=B7 Connectivity Components
=B7 Legacy Components
=B7 Management Tools
=B7 Notification Services Client Components
=B7 Reporting Services Report Manager
=B7 Reporting Services Shared Tools
=B7 SQL Server 2005 Shared Tools
=B7 Software Development Kit
=B7 SQLXML Client Features
=B7 SQL Server 2005 Books Online
=B7 SQL Server Mobile Server ToolsDataPro wrote:
> Hi:
> Our developer's are supposed to use SQL Server Developer Edition Client
> Tools Only.
> Can anybody tell me if any of the components below could be considered
> as that tool?
> Many thanks in advance.
> Analysis Services Shared Tools
> Business Intelligence Development Studio
> Connectivity Components
> Legacy Components
> Management Tools
> Notification Services Client Components
> Reporting Services Report Manager
> Reporting Services Shared Tools
> SQL Server 2005 Shared Tools
> Software Development Kit
> SQLXML Client Features
> SQL Server 2005 Books Online
> SQL Server Mobile Server Tools
>
Those are basic SQL Server components. You're asking the wrong
question, it's not the components that you need to worry about, it's
where they were installed from. Were they installed from SQL Server
Developer Edition media, or one of the other editions?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Our software aquisition folks tell me that they were in the contract as
sub components of SQL Server 2005 Standard and Enterprise Editions.
Does that make sense?
I was told that if one attempted to install SQL Server on a server that
could work. However attempting to install it on a workstation would
only allow the installation of Query Analyzer. So I'm not sure if any
other client tools could be installed that way.
Thanks for the help.
Tracy McKibben wrote:
> DataPro wrote:
> Those are basic SQL Server components. You're asking the wrong
> question, it's not the components that you need to worry about, it's
> where they were installed from. Were they installed from SQL Server
> Developer Edition media, or one of the other editions?
>=20
>=20
> --=20
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Question on DEveloper EDition Client Tools Only

Hi:
Our developer's are supposed to use SQL Server Developer Edition Client
Tools Only.
Can anybody tell me if any of the components below could be considered
as that tool?
Many thanks in advance.
Analysis Services Shared Tools
=B7 Business Intelligence Development Studio
=B7 Connectivity Components
=B7 Legacy Components
=B7 Management Tools
=B7 Notification Services Client Components
=B7 Reporting Services Report Manager
=B7 Reporting Services Shared Tools
=B7 SQL Server 2005 Shared Tools
=B7 Software Development Kit
=B7 SQLXML Client Features
=B7 SQL Server 2005 Books Online
=B7 SQL Server Mobile Server ToolsDataPro wrote:
> Hi:
> Our developer's are supposed to use SQL Server Developer Edition Client
> Tools Only.
> Can anybody tell me if any of the components below could be considered
> as that tool?
> Many thanks in advance.
> Analysis Services Shared Tools
> · Business Intelligence Development Studio
> · Connectivity Components
> · Legacy Components
> · Management Tools
> · Notification Services Client Components
> · Reporting Services Report Manager
> · Reporting Services Shared Tools
> · SQL Server 2005 Shared Tools
> · Software Development Kit
> · SQLXML Client Features
> · SQL Server 2005 Books Online
> · SQL Server Mobile Server Tools
>
Those are basic SQL Server components. You're asking the wrong
question, it's not the components that you need to worry about, it's
where they were installed from. Were they installed from SQL Server
Developer Edition media, or one of the other editions?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Our software aquisition folks tell me that they were in the contract as
sub components of SQL Server 2005 Standard and Enterprise Editions.
Does that make sense?
I was told that if one attempted to install SQL Server on a server that
could work. However attempting to install it on a workstation would
only allow the installation of Query Analyzer. So I'm not sure if any
other client tools could be installed that way.
Thanks for the help.
Tracy McKibben wrote:
> DataPro wrote:
> > Hi:
> >
> > Our developer's are supposed to use SQL Server Developer Edition Client
> > Tools Only.
> >
> > Can anybody tell me if any of the components below could be considered
> > as that tool?
> >
> > Many thanks in advance.
> >
> > Analysis Services Shared Tools
> >
> > =B7 Business Intelligence Development Studio
> >
> > =B7 Connectivity Components
> >
> > =B7 Legacy Components
> >
> > =B7 Management Tools
> >
> > =B7 Notification Services Client Components
> >
> > =B7 Reporting Services Report Manager
> >
> > =B7 Reporting Services Shared Tools
> >
> > =B7 SQL Server 2005 Shared Tools
> >
> > =B7 Software Development Kit
> >
> > =B7 SQLXML Client Features
> >
> > =B7 SQL Server 2005 Books Online
> >
> > =B7 SQL Server Mobile Server Tools
> >
> Those are basic SQL Server components. You're asking the wrong
> question, it's not the components that you need to worry about, it's
> where they were installed from. Were they installed from SQL Server
> Developer Edition media, or one of the other editions?
> > > -- > Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Question on Connectivity tools for SQL 2000 and SQL 2005

Question on just connectivity tools for SQL 2000 and SQL 2005
We are in the process of doing a inplace-upgrade of our SQL Server 2000
to SQL Server 2005. Currently all of the client computers have only the
connectivity tools from SQL 2000 installed in them. Is it necessary to
upgrade all the client machines with new SQL 2005 connectivity tools?
Any advice in this regard will be greatly appreciated.
Question on Client tools for SQL 2000 and SQL 2005
The other question I have is I have a unique client that has SQL 2000
Client tools installed, I am planning to also install the SQL 2005
Client tools, in this scenario when the Client connects to the Server
which client setting does it take. So for instance if in the SQL
Serever 2000 Network Client utility if I have only tcp_ip enabled as
the network protocol and on SQL 2005 if I have only Namedpipes enabled,
how does SQL Server figure out which setting should it look at? Do I
need to keep them consistent for both?
ThanksHi
Without upgrading the clients you will not have access to the facilities
available to the Native Client although this may not be a problem immediatel
y
after upgrading.
Depending on what you require the client tools for, then you may not need to
upgrade them, but you will not have any of the SQL 2005 specific features
available. The protocol used by your application will depend on what you hav
e
specified in the connection string, installing SQL 2005 may give you more
updated versions of the component you use.
If you are not using SQL 2000, I would look at removing the SQL 2000 tools.
HTH
John
"shub" wrote:

> Question on just connectivity tools for SQL 2000 and SQL 2005
> We are in the process of doing a inplace-upgrade of our SQL Server 2000
> to SQL Server 2005. Currently all of the client computers have only the
> connectivity tools from SQL 2000 installed in them. Is it necessary to
> upgrade all the client machines with new SQL 2005 connectivity tools?
> Any advice in this regard will be greatly appreciated.
> Question on Client tools for SQL 2000 and SQL 2005
> The other question I have is I have a unique client that has SQL 2000
> Client tools installed, I am planning to also install the SQL 2005
> Client tools, in this scenario when the Client connects to the Server
> which client setting does it take. So for instance if in the SQL
> Serever 2000 Network Client utility if I have only tcp_ip enabled as
> the network protocol and on SQL 2005 if I have only Namedpipes enabled,
> how does SQL Server figure out which setting should it look at? Do I
> need to keep them consistent for both?
> Thanks
>

Question on Connectivity tools for SQL 2000 and SQL 2005

Question on just connectivity tools for SQL 2000 and SQL 2005
We are in the process of doing a inplace-upgrade of our SQL Server 2000
to SQL Server 2005. Currently all of the client computers have only the
connectivity tools from SQL 2000 installed in them. Is it necessary to
upgrade all the client machines with new SQL 2005 connectivity tools?
Any advice in this regard will be greatly appreciated.
Question on Client tools for SQL 2000 and SQL 2005
The other question I have is I have a unique client that has SQL 2000
Client tools installed, I am planning to also install the SQL 2005
Client tools, in this scenario when the Client connects to the Server
which client setting does it take. So for instance if in the SQL
Serever 2000 Network Client utility if I have only tcp_ip enabled as
the network protocol and on SQL 2005 if I have only Namedpipes enabled,
how does SQL Server figure out which setting should it look at? Do I
need to keep them consistent for both?
ThanksHi
Without upgrading the clients you will not have access to the facilities
available to the Native Client although this may not be a problem immediately
after upgrading.
Depending on what you require the client tools for, then you may not need to
upgrade them, but you will not have any of the SQL 2005 specific features
available. The protocol used by your application will depend on what you have
specified in the connection string, installing SQL 2005 may give you more
updated versions of the component you use.
If you are not using SQL 2000, I would look at removing the SQL 2000 tools.
HTH
John
"shub" wrote:
> Question on just connectivity tools for SQL 2000 and SQL 2005
> We are in the process of doing a inplace-upgrade of our SQL Server 2000
> to SQL Server 2005. Currently all of the client computers have only the
> connectivity tools from SQL 2000 installed in them. Is it necessary to
> upgrade all the client machines with new SQL 2005 connectivity tools?
> Any advice in this regard will be greatly appreciated.
> Question on Client tools for SQL 2000 and SQL 2005
> The other question I have is I have a unique client that has SQL 2000
> Client tools installed, I am planning to also install the SQL 2005
> Client tools, in this scenario when the Client connects to the Server
> which client setting does it take. So for instance if in the SQL
> Serever 2000 Network Client utility if I have only tcp_ip enabled as
> the network protocol and on SQL 2005 if I have only Namedpipes enabled,
> how does SQL Server figure out which setting should it look at? Do I
> need to keep them consistent for both?
> Thanks
>

Question on Connectivity tools for SQL 2000 and SQL 2005

Question on just connectivity tools for SQL 2000 and SQL 2005
We are in the process of doing a inplace-upgrade of our SQL Server 2000
to SQL Server 2005. Currently all of the client computers have only the
connectivity tools from SQL 2000 installed in them. Is it necessary to
upgrade all the client machines with new SQL 2005 connectivity tools?
Any advice in this regard will be greatly appreciated.
Question on Client tools for SQL 2000 and SQL 2005
The other question I have is I have a unique client that has SQL 2000
Client tools installed, I am planning to also install the SQL 2005
Client tools, in this scenario when the Client connects to the Server
which client setting does it take. So for instance if in the SQL
Serever 2000 Network Client utility if I have only tcp_ip enabled as
the network protocol and on SQL 2005 if I have only Namedpipes enabled,
how does SQL Server figure out which setting should it look at? Do I
need to keep them consistent for both?
Thanks
Hi
Without upgrading the clients you will not have access to the facilities
available to the Native Client although this may not be a problem immediately
after upgrading.
Depending on what you require the client tools for, then you may not need to
upgrade them, but you will not have any of the SQL 2005 specific features
available. The protocol used by your application will depend on what you have
specified in the connection string, installing SQL 2005 may give you more
updated versions of the component you use.
If you are not using SQL 2000, I would look at removing the SQL 2000 tools.
HTH
John
"shub" wrote:

> Question on just connectivity tools for SQL 2000 and SQL 2005
> We are in the process of doing a inplace-upgrade of our SQL Server 2000
> to SQL Server 2005. Currently all of the client computers have only the
> connectivity tools from SQL 2000 installed in them. Is it necessary to
> upgrade all the client machines with new SQL 2005 connectivity tools?
> Any advice in this regard will be greatly appreciated.
> Question on Client tools for SQL 2000 and SQL 2005
> The other question I have is I have a unique client that has SQL 2000
> Client tools installed, I am planning to also install the SQL 2005
> Client tools, in this scenario when the Client connects to the Server
> which client setting does it take. So for instance if in the SQL
> Serever 2000 Network Client utility if I have only tcp_ip enabled as
> the network protocol and on SQL 2005 if I have only Namedpipes enabled,
> how does SQL Server figure out which setting should it look at? Do I
> need to keep them consistent for both?
> Thanks
>