By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,265 Members | 1,343 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,265 IT Pros & Developers. It's quick & easy.

Transfer from 2000 to 7.0 - what can be done?

P: n/a
I have a log file that went out of control (147GB), I feel that doing a shrink on the file/database would be time consuming so I am thinking of recreating the database from an imported version from our test server.

I know that data can flow from one SQL server to another without regard to the SQL server version but can tables, stored procedures and views export from a 2000 database and put back into a 7.0 database?

Thanks

--
Message posted via http://www.sqlmonster.com
Jul 23 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
JD
I would think that you may want to find out why your log file grew the way
it. It is likely to happen again, thereby making it a waste of time to try
and restore from 2000 to 7.0. Is your data no good? If not then why waste
time doing restores?

Do you have a space issue with your hard drives? It may be better to leave
the log file alone. But that could depend on what type of processing your
database is doing?

You can schedule the shrinking of the database for off hours or low usage
time.

Just some thoughts.
"Jeffrey Sheldon via SQLMonster.com" <fo***@SQLMonster.com> wrote in message
news:02******************************@SQLMonster.c om...
I have a log file that went out of control (147GB), I feel that doing a shrink on the file/database would be time consuming so I am thinking of
recreating the database from an imported version from our test server.
I know that data can flow from one SQL server to another without regard to the SQL server version but can tables, stored procedures and views export
from a 2000 database and put back into a 7.0 database?
Thanks

--
Message posted via http://www.sqlmonster.com

Jul 23 '05 #2

P: n/a

"Jeffrey Sheldon via SQLMonster.com" <fo***@SQLMonster.com> wrote in message
news:02******************************@SQLMonster.c om...
I have a log file that went out of control (147GB), I feel that doing a
shrink on the file/database would be time consuming so I am thinking of
recreating the database from an imported version from our test server.

I know that data can flow from one SQL server to another without regard to
the SQL server version but can tables, stored procedures and views export
from a 2000 database and put back into a 7.0 database?

Thanks

--
Message posted via http://www.sqlmonster.com


You can't restore a SQL 2000 backup on a SQL 7 server, so you would have to
recreate all the objects (and remove or rewrite all references to any
2000-only syntax or features), then copy the data with DTS, bcp.exe or
whatever.

It would probably be much easier to work out why your log file is so large,
and just shrink it - if you're concerned about the time required, then you
can do it in several steps and/or scheduled for a quiet time:

http://support.microsoft.com/kb/317375/EN-US/
http://support.microsoft.com/default...&Product=sql2k

Simon
Jul 23 '05 #3

P: n/a
Thanks for the responses. I am trying to avoid the shrink file since there is no way to determine how long it will take a 157GB log file to shrink.

I will look at the links provided. We know why the log file grew and we have put a stop to it. Now it is just time to find to shrink it.

Thanks to all again.

Jeff

--
Message posted via http://www.sqlmonster.com
Jul 23 '05 #4

P: n/a
Jeffrey Sheldon via SQLMonster.com (fo***@SQLMonster.com) writes:
I have a log file that went out of control (147GB), I feel that doing a
shrink on the file/database would be time consuming so I am thinking of
recreating the database from an imported version from our test server.

I know that data can flow from one SQL server to another without regard
to the SQL server version but can tables, stored procedures and views
export from a 2000 database and put back into a 7.0 database?


You would have to script, and it could still fail, if you are using
features that are available on SQL7.

I haven't tried it, but wouldn't a backup of the database, and then restore
into a new one circumvent the problem? Once the copy is up, you can drop
the old database with its 147 GB log.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.