Re: changing db location on sql2000
- From: "Kevin3NF" <kevin@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Feb 2008 08:37:45 -0600
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. ======================================================
.
- Follow-Ups:
- Re: changing db location on sql2000
- From: Tibor Karaszi
- Re: changing db location on sql2000
- References:
- changing db location on sql2000
- From: cj
- Re: changing db location on sql2000
- From: Kevin3NF
- Re: changing db location on sql2000
- From: cj
- Re: changing db location on sql2000
- From: Kevin3NF
- Re: changing db location on sql2000
- From: cj
- Re: changing db location on sql2000
- From: cj
- Re: changing db location on sql2000
- From: Charles Wang[MSFT]
- Re: changing db location on sql2000
- From: cj
- changing db location on sql2000
- Prev by Date: Re: changing db location on sql2000
- Next by Date: SQL 7 multiple NICs
- Previous by thread: Re: changing db location on sql2000
- Next by thread: Re: changing db location on sql2000
- Index(es):
Relevant Pages
|