MSSQL7.0 and windows2003

Hi,
Could anyone let me know if MSSQL7.0 is compatible with
windows2003? If so, is there any document of upgrade from
MSSQL7.0 from WinNT4.0 to Windows2003 enviroment ?
regards,
bharathHi,
No, You cant install SQL 7 in Win 2003 server, Only SQL server 2000 SP3 is
allowed in Windows 2003
Thanks
Hari
MCDBA
"bharath" <anonymous@.discussions.microsoft.com> wrote in message
news:b94b01c407f8$b5ca62c0$a401280a@.phx.gbl...
> Hi,
> Could anyone let me know if MSSQL7.0 is compatible with
> windows2003? If so, is there any document of upgrade from
> MSSQL7.0 from WinNT4.0 to Windows2003 enviroment ?
> regards,
> bharath|||Hi hari,
Thanks... is there any microsoft website url that says so?
regrds,
bharath
>--Original Message--
>Hi,
>No, You cant install SQL 7 in Win 2003 server, Only SQL
server 2000 SP3 is
>allowed in Windows 2003
>Thanks
>Hari
>MCDBA
>
>"bharath" <anonymous@.discussions.microsoft.com> wrote in
message
>news:b94b01c407f8$b5ca62c0$a401280a@.phx.gbl...
from
>
>.
>|||Yes Bharath, Have a look into the below website,
http://support.microsoft.com/?kbid=810391
Thanks
Hari
MCDBA
"bharath" <anonymous@.discussions.microsoft.com> wrote in message
news:b9ca01c40804$ba66b0c0$a401280a@.phx.gbl...
> Hi hari,
> Thanks... is there any microsoft website url that says so?
> regrds,
> bharath
> server 2000 SP3 is
> message
> from|||Here is another link that may be helpful:
http://www.microsoft.com/sql/howtob...snetsupport.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply only to the newsgroup.
"bharath" <anonymous@.discussions.microsoft.com> wrote in message
news:b9ca01c40804$ba66b0c0$a401280a@.phx.gbl...
> Hi hari,
> Thanks... is there any microsoft website url that says so?
> regrds,
> bharath
> server 2000 SP3 is
> message
> from

mssql7 to mssql200 transfer tables

I have a table in mssql7 that has 7000000 record and I want to take
100000 records out of it and place them into the new machine with
mssql2000. The new machine will also have the same table name, so I
want to append the 100000 records into that table.

Thanks,
Royal344
--
Direct access to this group with http://web2news.com
http://web2news.com/?comp.databases.ms-sqlserverroyal344 (royal344.news.invalid@.web2news.net) writes:
> I have a table in mssql7 that has 7000000 record and I want to take
> 100000 records out of it and place them into the new machine with
> mssql2000. The new machine will also have the same table name, so I
> want to append the 100000 records into that table.

Do you want any 100000 rows?

You could use BCP and make use of the options for specifying first and
last row. I don't recall the exact name for these options right, but
you can look up the syntax for BCP in Books Online.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

MsSql7 merge replication error

Greetings colleagues!

I recently set up replication between a Windows2000/Mssql7 server set up as distributor/publisher, and outside the firewall, an NT4/Mssql7 server.

I tried to set up Merge replication and initially i got the error 14010 whenever i tried to push a publication from the dist./pub. to the subscriber. This i fixed by having an alias created within the domain "inside" the firewall protected area, for the server in the DMZ(which was known until then only by its IP number).
I simply canceled the test publications and recreated them.

At first glance everything seemed to work perfectly until i got the error for the merge agent: 20084 , subscription cannot be accepted by subscriber database, An error i understand only to appear in the case of PULL subscription, yet i had only used PUSH subscriptions from the dist./pub. server.

I have to admit i'm mystified by this error, and having perused books online, Microsoft/technet and other sources i'm no closer to solving the problem.

I would really appreciated any help in fixing the problem and get my replication running.
Thank you very much, Vincent Seghers, Programmer-Analyst
Gent.beThe problem turned out to be a reference to a server on its actual IP "name" and not its nam. I declared an Alias (lettername short, no special characters) in the Client Network utility and it worked fine from then on.

Originally posted by VincentJS
Greetings colleagues!

I recently set up replication between a Windows2000/Mssql7 server set up as distributor/publisher, and outside the firewall, an NT4/Mssql7 server.

I tried to set up Merge replication and initially i got the error 14010 whenever i tried to push a publication from the dist./pub. to the subscriber. This i fixed by having an alias created within the domain "inside" the firewall protected area, for the server in the DMZ(which was known until then only by its IP number).
I simply canceled the test publications and recreated them.

At first glance everything seemed to work perfectly until i got the error for the merge agent: 20084 , subscription cannot be accepted by subscriber database, An error i understand only to appear in the case of PULL subscription, yet i had only used PUSH subscriptions from the dist./pub. server.

I have to admit i'm mystified by this error, and having perused books online, Microsoft/technet and other sources i'm no closer to solving the problem.

I would really appreciated any help in fixing the problem and get my replication running.
Thank you very much, Vincent Seghers, Programmer-Analyst
Gent.be

MSSQL7 end of support

Hi,
Can anyone confirm when SQL7 will reach end of support (end of life)?
I assume this will happen in Nov with release of SQL2005 but need some
definite confirmation.
I don't seem to be able to find this on Microsoft's website.
Thanks.
Hi
http://support.microsoft.com/lifecycle/?p1=2862
Mainstream: 2005-12-31
Extended: 2010-12-31
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sysbox27" wrote:

> Hi,
> Can anyone confirm when SQL7 will reach end of support (end of life)?
> I assume this will happen in Nov with release of SQL2005 but need some
> definite confirmation.
> I don't seem to be able to find this on Microsoft's website.
> Thanks.
|||Many thanks Mike.
I can't however seem to be able to call up that page you provided. Will try
again later.
Cheers,
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> http://support.microsoft.com/lifecycle/?p1=2862
> Mainstream: 2005-12-31
> Extended: 2010-12-31
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "sysbox27" wrote:

MSSQL7 end of support

Hi,
Can anyone confirm when SQL7 will reach end of support (end of life)?
I assume this will happen in Nov with release of SQL2005 but need some
definite confirmation.
I don't seem to be able to find this on Microsoft's website.
Thanks.Hi
http://support.microsoft.com/lifecycle/?p1=2862
Mainstream: 2005-12-31
Extended: 2010-12-31
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sysbox27" wrote:
> Hi,
> Can anyone confirm when SQL7 will reach end of support (end of life)?
> I assume this will happen in Nov with release of SQL2005 but need some
> definite confirmation.
> I don't seem to be able to find this on Microsoft's website.
> Thanks.|||Many thanks Mike.
I can't however seem to be able to call up that page you provided. Will try
again later.
Cheers,
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> http://support.microsoft.com/lifecycle/?p1=2862
> Mainstream: 2005-12-31
> Extended: 2010-12-31
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "sysbox27" wrote:
> > Hi,
> > Can anyone confirm when SQL7 will reach end of support (end of life)?
> > I assume this will happen in Nov with release of SQL2005 but need some
> > definite confirmation.
> > I don't seem to be able to find this on Microsoft's website.
> > Thanks.

MSSQL7 end of support

Hi,
Can anyone confirm when SQL7 will reach end of support (end of life)?
I assume this will happen in Nov with release of SQL2005 but need some
definite confirmation.
I don't seem to be able to find this on Microsoft's website.
Thanks.Hi
http://support.microsoft.com/lifecycle/?p1=2862
Mainstream: 2005-12-31
Extended: 2010-12-31
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sysbox27" wrote:

> Hi,
> Can anyone confirm when SQL7 will reach end of support (end of life)?
> I assume this will happen in Nov with release of SQL2005 but need some
> definite confirmation.
> I don't seem to be able to find this on Microsoft's website.
> Thanks.|||Many thanks Mike.
I can't however seem to be able to call up that page you provided. Will try
again later.
Cheers,
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> http://support.microsoft.com/lifecycle/?p1=2862
> Mainstream: 2005-12-31
> Extended: 2010-12-31
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "sysbox27" wrote:
>

MSSQL7 and WinXP

Hi!
We're closer to a solution to our problem with slow machines on a MSDE
database (two weeks ago).
We now have one standalone machine that runs MSSQL7, SP4 (SP4 was
installed after it did not work without it).
The computer has been freshly set up with WinXPPro, MSSQL7 and our
application. All current Windowsupdates applied afterwards.
OK, what we have now:
1) Extremely quick resutls when using osql
2) Extremely slow startup time of our application. (Delphi, using ADO as
connection)
The reason for 2) is (or rather one effect of it) can be seen in the error
log:
--8<--
2004-06-17 15:14:19.43 spid5 Startet Datenbank 'Patient'.
2004-06-17 15:14:19.43 spid5 Opening file C:\MSSQL7\data\Patient.mdf.
2004-06-17 15:14:19.43 spid5 Opening file
C:\MSSQL7\data\Patient_log.LDF.
2004-06-17 15:14:20.01 spid14 Closing file C:\MSSQL7\data\Stammdaten.mdf.
2004-06-17 15:14:20.01 spid14 Closing file
C:\MSSQL7\data\Stammdaten_log.LDF.
--8<--
Sections like this one are repeated *quite* often, read: immediately
afterwards. Several times. For approx.10 seconds per database. (which
makes about 10-20 retries).
We then noticed that this machine has hyperthreading enabled, which we
disabled. The entries in the log file were reduced to a more sensible
amount, still it happens more often than on other machines with our
software and MSSQL7 or MSDE.
Question: What else can we do? Is there something with respect to
hyperthreading that can still interfere? Have others also seen multiple
repeating entries in the log files and have a clue as to where they come
from?
Thanks for reading,
Stefan
See the BOL for information concerning the AUTO_CLOSE option. It appears to
me that you have that enabled (the default for MSDE) and the database server
is closing the database after all connected clients are disconnected.
Jim
"Stefan M. Huber" <looseleaf@.gmx.net> wrote in message
news:opr9qpvxj0s9ddfw@.news.individual.de...
> Hi!
> We're closer to a solution to our problem with slow machines on a MSDE
> database (two weeks ago).
> We now have one standalone machine that runs MSSQL7, SP4 (SP4 was
> installed after it did not work without it).
> The computer has been freshly set up with WinXPPro, MSSQL7 and our
> application. All current Windowsupdates applied afterwards.
> OK, what we have now:
> 1) Extremely quick resutls when using osql
> 2) Extremely slow startup time of our application. (Delphi, using ADO as
> connection)
> The reason for 2) is (or rather one effect of it) can be seen in the error
> log:
> --8<--
> 2004-06-17 15:14:19.43 spid5 Startet Datenbank 'Patient'.
> 2004-06-17 15:14:19.43 spid5 Opening file C:\MSSQL7\data\Patient.mdf.
> 2004-06-17 15:14:19.43 spid5 Opening file
> C:\MSSQL7\data\Patient_log.LDF.
> 2004-06-17 15:14:20.01 spid14 Closing file
C:\MSSQL7\data\Stammdaten.mdf.
> 2004-06-17 15:14:20.01 spid14 Closing file
> C:\MSSQL7\data\Stammdaten_log.LDF.
> --8<--
> Sections like this one are repeated *quite* often, read: immediately
> afterwards. Several times. For approx.10 seconds per database. (which
> makes about 10-20 retries).
> We then noticed that this machine has hyperthreading enabled, which we
> disabled. The entries in the log file were reduced to a more sensible
> amount, still it happens more often than on other machines with our
> software and MSSQL7 or MSDE.
> Question: What else can we do? Is there something with respect to
> hyperthreading that can still interfere? Have others also seen multiple
> repeating entries in the log files and have a clue as to where they come
> from?
> Thanks for reading,
> Stefan
>
|||On Fri, 18 Jun 2004 09:44:47 -0700, Jim Young <thorium48@.hotmail.com>
wrote:

> See the BOL for information concerning the AUTO_CLOSE option. It appears
> to me that you have that enabled (the default for MSDE) and the database
> server is closing the database after all connected clients are
> disconnected.
Thanks for the pointer. However, I wonder, why this happens when only one
single client wants to connect at startup. I'll check that next time I am
at work. Thanks.
Stefan
"Mobile launchers are more difficult to detect because they move
around, unlike fixed launchers."
-- Katie Couric, NBC News

MSSQL7 and Windows 2000

Dear All,
could you please tell me if MSSQL7 is compliant with Windows 2000 ?
Which Service Pack is needed from both MSSQL and W2000 ?
many thanks in advance for your help ;)it's fine... you should be using the latest service packs for each of them|||Ok, thanks for your reply :)

MSSQL7 -> MSSQL2000 schema and data

Hi group,
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.
> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.

> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.

> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.

> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.

> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.

> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.

> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com
|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller

MSSQL7 -> MSSQL2000 schema and data

Hi group,
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.

> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.

> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.

> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.

> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.

> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.

> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller

MSSQL7 -> MSSQL2000 schema and data

Hi group,
[First time in, so feel free to shoot me if needed]
I am experienced with Postgresql, but relatively new to MSSQLServer.
I am building an application that uses MSSQL7.
Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
No DTS, complex userstuff and that.
The target MSSQLServer will be 2000.
So now I need to know how to get my databaseschema and content from 7 to
2000.
As far as I can tell the option: GENERATE SQL only offers me an text-based
instruction for SCHEMA, not the content of table.
Right?
Question: Will MSSQL2000 understand the instructions created by MSSQL7?
As for the data itself:
The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
found is by backing the whole thing up, as a binary.
(Using 'all tasks' --> 'Backup database')
Question: Will MSSQL2000 read and understand this file?
And will I need the databaseschema as generated by the GENERATE SQL option?
Or will MSSQL2000 be able to get that from the binary export?
Is this the way to do it, or am I missing lots of stuff?
Thanks for your time
Regards,
Erwin Moller
PS: I am sorry, but expect this is a very basic question. I just cannot find
any clear material on the subject online.> I am building an application that uses MSSQL7.
> Only basic stuff: 20 tables, foreign keys, a nice diagram, a few indexes.
> No DTS, complex userstuff and that.
> The target MSSQLServer will be 2000.
> So now I need to know how to get my databaseschema and content from 7 to
> 2000.
> As far as I can tell the option: GENERATE SQL only offers me an text-based
> instruction for SCHEMA, not the content of table.
> Right?
Right.
> Question: Will MSSQL2000 understand the instructions created by MSSQL7?
Yes.
> As for the data itself:
> The only way to export the data in the tables from MSSQL7 to MSSQL2000 I
> found is by backing the whole thing up, as a binary.
> (Using 'all tasks' --> 'Backup database')
You found the easiest way. You could use Data transformation Services (DTS),
for example, as well.
> Question: Will MSSQL2000 read and understand this file?
Yes, simply restore the backup on SQL 2000 box. But I guess you will have to
change the physical path to data and log files, unless you have created the
database in 7.0 in your custom (not SQL default) folder and you have the
same directory structure in 2000.
> And will I need the databaseschema as generated by the GENERATE SQL
> option?
No.
> Or will MSSQL2000 be able to get that from the binary export?
Yes - backup has everything, schema and data.
> Is this the way to do it, or am I missing lots of stuff?
Yes, this is a good way. You have original 7.0 db, backup and new 2000 db
after the action. So. if anything goes wrong, you have 3 copies. And the
process is quite simple.
--
Dejan Sarka, SQL Server MVP
Mentor
www.SolidQualityLearning.com|||Thanks Dejan Sarka!
I seldom receive such to-the-point answers. :-)
Regards,
Erwin Moller

MSSQL7

I am a beginner with MSSQL7 so please bear with me. I am trying to open a
database that is approx 187KB in size. This file resides in the following
folder; C:\MSSQL7\DATA. This was restored from a backup we reterived from a
subjects computer. I obtained a copy of the MSSQL7 software. I was able to
load it on a standalone computer. This is as far as I can get. I want to be
able to copy the 187KB file in the approporiate folder of this newley
installed MSSQL7 program so I can simply open up the tables and see the data.
When I start Enterprise manager, I can't seem to connect it to this old
database.
Please help
cart34@.netzero.net
Have a look at these. You can use sp_attach_db to add it to the new server.
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Cart34" <Cart34@.discussions.microsoft.com> wrote in message
news:522E836E-979C-4D80-8823-949D3148A6A9@.microsoft.com...
>I am a beginner with MSSQL7 so please bear with me. I am trying to open a
> database that is approx 187KB in size. This file resides in the following
> folder; C:\MSSQL7\DATA. This was restored from a backup we reterived from
> a
> subjects computer. I obtained a copy of the MSSQL7 software. I was able
> to
> load it on a standalone computer. This is as far as I can get. I want to
> be
> able to copy the 187KB file in the approporiate folder of this newley
> installed MSSQL7 program so I can simply open up the tables and see the
> data.
> When I start Enterprise manager, I can't seem to connect it to this old
> database.
> Please help
> cart34@.netzero.net

mssql2000

Hi
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
Thanks
You can attach a 7 database to 2000. Another option is backup and restore. Just make sure you test
your applications...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks

mssql2000

Hi
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
--
ThanksYou can attach a 7 database to 2000. Another option is backup and restore. J
ust make sure you test
your applications...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks

mssql2000

Hi
I am changing my server from mssq7 to sql2000
Do i need to upgrade my mssql7 databse to 2000.
or only i want to just attach db to 2000 server.
thanks.
--
ThanksYou can attach a 7 database to 2000. Another option is backup and restore. Just make sure you test
your applications...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"shif" <ns_0001@.hotmail.com> wrote in message
news:214DE35F-B234-4519-8754-E7D14B317A91@.microsoft.com...
> Hi
> I am changing my server from mssq7 to sql2000
> Do i need to upgrade my mssql7 databse to 2000.
> or only i want to just attach db to 2000 server.
> thanks.
> --
> Thanks