When I copy a BACKUP using a .cmd file from a command-box in Win2K, like
this:
copy DBF_db_20040602.BAK .
it copies the entire file to the current directory where the cmd-file is
started.
So far so good...
But, when I change the cmd-file to do this:
copy DBF_db_20040602.BAK DBF_newfile.BAK
is only creates a file of only 6k in size. The original file is about 2 Gb
in size.
Anyone knows why this happens?
.Nicohi
Have u tried using xcopy?
J
"Nico" <duiken@.nospam.nl> wrote in message
news:40bdeb35$0$136$18b6e80@.news.wanadoo.nl...
> When I copy a BACKUP using a .cmd file from a command-box in Win2K, like
> this:
> copy DBF_db_20040602.BAK .
> it copies the entire file to the current directory where the cmd-file is
> started.
> So far so good...
> But, when I change the cmd-file to do this:
> copy DBF_db_20040602.BAK DBF_newfile.BAK
> is only creates a file of only 6k in size. The original file is about 2 Gb
> in size.
> Anyone knows why this happens?
> .Nico
>|||Nico,
Sounds strange. I suggest you post this to a windows forum, as likelyhood to find Windows experts should be
higher there... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Nico" <duiken@.nospam.nl> wrote in message news:40bdeb35$0$136$18b6e80@.news.wanadoo.nl...
> When I copy a BACKUP using a .cmd file from a command-box in Win2K, like
> this:
> copy DBF_db_20040602.BAK .
> it copies the entire file to the current directory where the cmd-file is
> started.
> So far so good...
> But, when I change the cmd-file to do this:
> copy DBF_db_20040602.BAK DBF_newfile.BAK
> is only creates a file of only 6k in size. The original file is about 2 Gb
> in size.
> Anyone knows why this happens?
> .Nico
>
No comments:
Post a Comment