copying Databases

I backed a MSSQL2000 database into a BAK file. Now when I create a
MSSQL2005 system and I goto RESTORE - after creating a database with the
same name- I get
"ERROR the backup set holds a database other than the existing "Toxinet'
database. RESTORE DATABASE is terminating abnormally"
Any ideas? This process has always worked in MSSQL97 & 2000
Thanks,
Raul Rego
NJPIES
rrego@.njpies.org
Hi Raul
From your limited information, it sounds like the name in the backup is not
what you think it is.
You don't have to create a database before doing a restore. Why don't you
just try restoring and letting the restore process create the database.
Perhaps there is a spelling issue or you have a case sensitive collation.
BTW, there was no MSSQL97. The version before SQL Server 2000 was SQL Server
7.
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Raul" <rrego@.njpies.org> wrote in message
news:BCE20BE9-3480-43A4-9B44-C6A0F628B38A@.microsoft.com...
>I backed a MSSQL2000 database into a BAK file. Now when I create a
>MSSQL2005 system and I goto RESTORE - after creating a database with the
>same name- I get
> "ERROR the backup set holds a database other than the existing "Toxinet'
> database. RESTORE DATABASE is terminating abnormally"
> Any ideas? This process has always worked in MSSQL97 & 2000
> Thanks,
> Raul Rego
> NJPIES
> rrego@.njpies.org
>
|||Use the "with replace" clause.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Raul" <rrego@.njpies.org> wrote in message
news:BCE20BE9-3480-43A4-9B44-C6A0F628B38A@.microsoft.com...
>I backed a MSSQL2000 database into a BAK file. Now when I create a
>MSSQL2005 system and I goto RESTORE - after creating a database with the
>same name- I get
> "ERROR the backup set holds a database other than the existing "Toxinet'
> database. RESTORE DATABASE is terminating abnormally"
> Any ideas? This process has always worked in MSSQL97 & 2000
> Thanks,
> Raul Rego
> NJPIES
> rrego@.njpies.org
>

copying Databases

I backed a MSSQL2000 database into a BAK file. Now when I create a
MSSQL2005 system and I goto RESTORE - after creating a database with the
same name- I get
"ERROR the backup set holds a database other than the existing "Toxinet'
database. RESTORE DATABASE is terminating abnormally"
Any ideas? This process has always worked in MSSQL97 & 2000
Thanks,
Raul Rego
NJPIES
rrego@.njpies.orgHi Raul
From your limited information, it sounds like the name in the backup is not
what you think it is.
You don't have to create a database before doing a restore. Why don't you
just try restoring and letting the restore process create the database.
Perhaps there is a spelling issue or you have a case sensitive collation.
BTW, there was no MSSQL97. The version before SQL Server 2000 was SQL Server
7.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Raul" <rrego@.njpies.org> wrote in message
news:BCE20BE9-3480-43A4-9B44-C6A0F628B38A@.microsoft.com...
>I backed a MSSQL2000 database into a BAK file. Now when I create a
>MSSQL2005 system and I goto RESTORE - after creating a database with the
>same name- I get
> "ERROR the backup set holds a database other than the existing "Toxinet'
> database. RESTORE DATABASE is terminating abnormally"
> Any ideas? This process has always worked in MSSQL97 & 2000
> Thanks,
> Raul Rego
> NJPIES
> rrego@.njpies.org
>|||Use the "with replace" clause.
--
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Raul" <rrego@.njpies.org> wrote in message
news:BCE20BE9-3480-43A4-9B44-C6A0F628B38A@.microsoft.com...
>I backed a MSSQL2000 database into a BAK file. Now when I create a
>MSSQL2005 system and I goto RESTORE - after creating a database with the
>same name- I get
> "ERROR the backup set holds a database other than the existing "Toxinet'
> database. RESTORE DATABASE is terminating abnormally"
> Any ideas? This process has always worked in MSSQL97 & 2000
> Thanks,
> Raul Rego
> NJPIES
> rrego@.njpies.org
>

Copying BAK file

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
hi
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
>

Copying BAK file

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...[vb
col=seagreen]
> 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
>[/vbcol]

Copying BAK file

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
>