Move MSSQL 2000 -> MSSQL 7 (HELP!)

I need to put a database that is on MSSQL 2000 to a machine that is running
MSSQL 7. Is this possible?
There should be nothing in the 2000 db that wouldn't go back to 7. It was
created from a MSSQL7 DB.
Thanks in advance,
RobYou can't just take a sql2k db and restore/attach it to sql7. The sql2k meta
data will not be understood by sql7. Your option is to use data transfer
(i.e. import/export - dts) to move data.
-oj
"Rob rent-right com>" <ryost --nospam-- <atdot> wrote in message
news:eRj5F4iOGHA.2088@.tk2msftngp13.phx.gbl...
>I need to put a database that is on MSSQL 2000 to a machine that is running
>MSSQL 7. Is this possible?
> There should be nothing in the 2000 db that wouldn't go back to 7. It was
> created from a MSSQL7 DB.
>
> Thanks in advance,
> Rob
>|||> I need to put a database that is on MSSQL 2000 to a machine that is
running
> MSSQL 7. Is this possible?
Perhaps this is a naive unorthodox approach to the answer, but here's my
outside-the-box idea... Try it and see what happens. As an experiment you
could attempt your scenario using the SQL Server 2000 Northwind and pubs
databases to punch down to SQL 7.

> There should be nothing in the 2000 db that wouldn't go back to 7. It was
> created from a MSSQL7 DB.
As a more exhaustive experiment, you could sit at your 2000 server, make a
Foo database, and create one object of every type: 1 database, 1 table, 1
column in the table of each data type, 1 clustered index, 1 nonclustered
index, 1 constraint, 1 login, 1 custom data type, 1 stored procedure, 1
view, 1 user defined function, 1 rule...you get the idea
and then try to punch that down to SQL 7.
If you document your results and experiences, that's the kind of stuff that
SQL Server Magazine might publish. It will make you famous & get you lots
and lots of women. Either that, or just nerd-points.
--
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei
"Rob rent-right com>" <ryost --nospam-- <atdot> wrote in message
news:eRj5F4iOGHA.2088@.tk2msftngp13.phx.gbl...
>
> Thanks in advance,
> Rob
>|||This worked, I created the database again with a sql script, and then use
import to move in the data.
Thanks,
rob
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23q6AmCjOGHA.3264@.TK2MSFTNGP11.phx.gbl...
> You can't just take a sql2k db and restore/attach it to sql7. The sql2k
> meta data will not be understood by sql7. Your option is to use data
> transfer (i.e. import/export - dts) to move data.
> --
> -oj
>
> "Rob rent-right com>" <ryost --nospam-- <atdot> wrote in message
> news:eRj5F4iOGHA.2088@.tk2msftngp13.phx.gbl...
>

Move Log Files From C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG To E:\MSSQL Logs

How do I move the default log files placed in: C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG to a different location? I want to place them in a partition I have setup which stores log files? Reason being is that this log directory is getting quite large, 600MB and I want to conserve space on my C:\ partition.

Thanks.

You can move the files using sp_detach_db and sp_attach_db. You can find the steps explained in the following article:

How to move SQL Server databases to a new location by using Detach and Attach functions in SQL Server

http://support.microsoft.com/kb/224071

-Sue

|||

Sue:

Acutally I dont want to move any database files, what I want to move is simply the log files, just errors, activity and such. The files reside in the /log directory not the /data directory.

Thanks for the help.

|||

For the SQL error log, open up SQL Server Configuration Manager. Select the SQL Services node, double click on SQL Server in the right pane and go to the advanced tab. View the startup parameters. The path following -e is for the error log. See the books online topic: Using the SQL Server Service Startup Options.

You can use Configuration Manager to change the path for SQL Agent as well. Select the service node, double click on SQL Server agent and go to the advanced tab. Change the path for the dump directory.

In terms of the default trace, that will default to your installation directory. You can create your own trace if you want another location.

-Sue

|||

Thanks Sue that did the trick.

Changed dump directory to: E:\MSSQL and startup parameters e to E:\MSSQL\ERRORLOG and restarted the service.

Move Images (BLOBs) from MSSQL to a folder

Hi Guys.

I have a MSSQL database of 2 gigs which has about 100mb of data, the rest is images.

I have noticed a huge decrease in performance as more images are entered into the database (most images are about 1mb).

I would like to know if there is a way to extract the images from the database and move them to a folder on the server.

Does anyone have experience or suggestions as to how this can be done?

Regards

VVOLTT

Quote:

Originally Posted by vvoltt

Hi Guys.

I have a MSSQL database of 2 gigs which has about 100mb of data, the rest is images.

I have noticed a huge decrease in performance as more images are entered into the database (most images are about 1mb).

I would like to know if there is a way to extract the images from the database and move them to a folder on the server.

Does anyone have experience or suggestions as to how this can be done?

Regards

VVOLTT

Before doing something like this, make sure that your SELECTS are optimized so that they don't pull images unnecessarily, and that your tables are properly indexed. Try taking a look at the execution plan for your slow queries.

The easiest way to do something like this would be to create a simple interface to query each row, and then write the data to a file.