Re: changing db location on sql2000



I definitely agree with Kevin.

However if that is for some reason not doable, you *might* be able to use trace flag 1807, but make sure you read below carefully first:
http://support.microsoft.com/default.aspx?scid=kb;en-us;304261

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx> wrote in message news:%23PJaA4kbIHA.4144@xxxxxxxxxxxxxxxxxxxxxxx
Can you not back this database up? backups do support UNC paths...and compress that thing while you're at it? :)

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.



"cj" <cj@xxxxxxxxxxxxx> wrote in message news:urliNekbIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
This is a unique situation where I'm sending a pc offsite to an isolated network with a tech to suck an informix database dry onto something that can be brought back here where some of the tables will have to be manipulated some and put into a new sql server system. It's one of those situations where doing something against standard practice is ok. Therefore I wish MS had let us decide if it was ok to use a usb or network share or whatever to store the data. I'm not upset. That's how life is and I'll live with it. I just wish MS had given us the capability.

Yes this usb drive is not a normal usb drive. It is a 2TB array in one enclosure looking like a standard usb drive. It gave me the ability to attach it to a pc via usb or attach it straight to an ethernet network. Either way I found I would have to attach a network drive to get to that space and apparently SQL 2000 desktop will not do that.



Charles Wang[MSFT] wrote:
Hi cj,
I think that your storage drive is not a common USB drive. This issue is not really caused by a USB drive but essentially caused by Network share. Since your USB drive was showed as a network share, SQL Server could not use it for storing database files. If your database is very large, you may consider using SAN, NAS etc which are fast and scalable network storage solutions. Appreciate your understanding that for a server product, adventure is always abstained, stability overwhelming everything. If your database is growing rapidly and your current disk has not enough space, you may consider shrinking your database files, increasing disk or migrating your storage to SAN or migrating your SQL Server to a more powerful server. Please feel free to let us know if you have any other questions or concerns. Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ======================================================
This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================




.



Relevant Pages

  • RE: Data storage solution advice sought...
    ... Data storage solution advice sought... ... > database, as it will allow. ... > my development), XML files, Pocket Access, SQL Server 2005 Mobile. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Data storage solution advice sought...
    ... someone with a storage card wth a 100MB db if they store images in the ... database, as it will allow. ... -Replicating with a SQL Server will not be offered as an option as this is ... Pocket Access - PROS: I understand that I can use ActiveSync wupport to ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Other Users dont see table updates
    ... Database systems are not real time network communication ... Where people really want real-time network ... people used sql server to send mail messages - ...
    (comp.databases.ms-access)
  • Re: changing db location on sql2000
    ... Can you not back this database up? ... backups do support UNC paths...and ... manipulated some and put into a new sql server system. ... Therefore I wish MS had let us decide if it was ok to use a usb or network ...
    (microsoft.public.sqlserver.setup)
  • ODBC Connection with SQL Managed Provider
    ... on a "network drive". ... database using the Microsoft .NET Framework 1.1 Data Provider for SQL ... authorizing the user against a table in the SQL server database. ... for the app to display the "splash" screen (which is the first thing it does ...
    (microsoft.public.dotnet.framework.adonet)