Help! Unable to restore DB from SQL7 to SQL2000

Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar Bear
Hi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name.Xmdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.lXdf'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>

Help! Unable to restore DB from SQL7 to SQL2000

Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name.­mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.l­df'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The backup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>sql

Help! Unable to restore DB from SQL7 to SQL2000

Hi Good Day everybody,
Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
below:
Current Server (Server A)
a) Windows NT4 SP6a
b) SQL 7 + SP4
c) Default Collation: SQL_Latin1_General_CP1_CI_AS
d) Default Data Location: E:\MSSQL7
New Server (Server B)
a) Window 2000 Server SP4
b) SQL 2000 + SP3a
c) Default Collation: Latin1_General_CP1_CI_AS (required to set as default)
d) Default Data Location: D:\Program Files\Microsoft SQL Server
Authentication Mode:
a) Mixed Mode
b) SQL and Windows Authentication
* Both server are login with same userid and password.
Problem:
I have create and new user database "PA_CCCTemp" in the SQL2000 server.
Besides, I also backup user database "PA_CCC" from SQL7.
However, during I restore databases that I have backup into the SQL2000
server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The back
up
set holds a backup of a database other than the existing 'PA_CCCTemp"
database. Restore Databse is terminating abnormally.
I do not know what is the problem caused. Either the database is different
name, or the restoration location are different from the original place, or
the collation is different.
I also need help on how I can migrate the database from SQL7 to SQL 2000,
includes user id and logon password.
Regards,
Polar BearHi,
It seems you have given a physical location which is not in the new server
(Drive and directory) while loading in SQL 2000.
Please follow the below steps in query analyzer:-
Restore filelistonly from disk='c:\backup\dbname.bak'
( replace the 'c:\backup\dbname.bak' with the actual backup file name with
path where the file resides.)
This will give you the Logical and Physical file names of the Backup file
name. While loading you should give the
correct logical file name and the place to keep the physical file. But
Physical file name can be a diffrent one.
Restore Database <dbname> from disk= 'c:\backup\dbname.bak' with
move 'logical_mdf_name' to 'c:\mssql\data\phys_data_name._mdf',
move 'logical_ldf_name' to 'c:\mssql\data\phys_log_name.l_df'
(Replace the logical_mdf_name and logical_ldf_name with the logical name you
got from RESTORE FILELISTONLY command.
Ensure that the directory give in physical file name is there in the server)
Thanks
Hari
SQL Server MVP
Thanks
Hari
SQL Server MVP
"Polar Bear" <Polar Bear@.discussions.microsoft.com> wrote in message
news:227A549B-7D5A-48DA-A4F5-1850CE31B84B@.microsoft.com...
> Hi Good Day everybody,
> Currently, I'm planning to upgrade SQL7 to SQL2000, the configuration are
> below:
> Current Server (Server A)
> a) Windows NT4 SP6a
> b) SQL 7 + SP4
> c) Default Collation: SQL_Latin1_General_CP1_CI_AS
> d) Default Data Location: E:\MSSQL7
> New Server (Server B)
> a) Window 2000 Server SP4
> b) SQL 2000 + SP3a
> c) Default Collation: Latin1_General_CP1_CI_AS (required to set as
> default)
> d) Default Data Location: D:\Program Files\Microsoft SQL Server
> Authentication Mode:
> a) Mixed Mode
> b) SQL and Windows Authentication
> * Both server are login with same userid and password.
> Problem:
> I have create and new user database "PA_CCCTemp" in the SQL2000 server.
> Besides, I also backup user database "PA_CCC" from SQL7.
> However, during I restore databases that I have backup into the SQL2000
> server, I hit an error "Microsoft SQL-DMo [ODBC SQLState:42000] The ba
ckup
> set holds a backup of a database other than the existing 'PA_CCCTemp"
> database. Restore Databse is terminating abnormally.
> I do not know what is the problem caused. Either the database is different
> name, or the restoration location are different from the original place,
> or
> the collation is different.
> I also need help on how I can migrate the database from SQL7 to SQL 2000,
> includes user id and logon password.
> Regards,
> Polar Bear
>

HELP! Restore SQL7 database to SQL2000 SP3a problem

I have a small database that urgently needs restoring under SQL 2000.
SP3a is installed.
Is there a procedure?
Yes.
First obtain three chickens and a mule...
Seriously, a SQL 7.0 database can be restored (or attached after detach) to
a SQL 2000 instance using the normal restore database commands or Enterprise
Manager. There is no difference in restoring a 7.0 backup to a SQL 2000
server than in restoring a SQL 2000 backup to a SQL 2000 server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132770162.841008.102880@.o13g2000cwo.googlegr oups.com...
>I have a small database that urgently needs restoring under SQL 2000.
> SP3a is installed.
> Is there a procedure?
>
|||You can use a RESTORE DATABASE command. For example:
RESTORE DATABASE MyDatabase
FROM DISK='C:\Backups\MyDatabase.bak'
WITH REPLACE
See the Books Online for details.
Hope this helps.
Dan Guzman
SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132770162.841008.102880@.o13g2000cwo.googlegr oups.com...
>I have a small database that urgently needs restoring under SQL 2000.
> SP3a is installed.
> Is there a procedure?
>
|||Thanks Geoff,
The error I am getting is:
SQL-DMO (ODBC SQLstate: 42000)
The media set for database (name) has 2 family members but only 1 are
provided. All members must be provided. Restore database is
terminating... "
S.
|||Evidently your backup spanned multiple backup sets (files or tapes). You
need to specify all backup sets in a single restore command:
RESTORE DATABASE MySQL7Database
FROM C:\Backups\MySQL7Backup1.bak,C:\Backups\MySQL7Back up2.bak
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132773276.165857.173410@.z14g2000cwz.googlegr oups.com...
> Thanks Geoff,
> The error I am getting is:
> SQL-DMO (ODBC SQLstate: 42000)
> The media set for database (name) has 2 family members but only 1 are
> provided. All members must be provided. Restore database is
> terminating... "
> S.
>
|||Geoff, thanks
No, this was not the case. The database backup file was created in SQL
Server 7 (SP4) and zips to 2MB after backup.
On selection of the database file it's backup set properties can be
seen. I selected to restore All, and there is no existing database over
which it will overwrite. So it is hard to see why it should be asking
for another file.
Are there any other settings that can be changed? I am having a look...
S.
|||Well guys, thanks very much anyway. I have tried using Dan Guzman's
suggestion of running a command script, but still no good - same error
type. I suppose that somehow there must be a corruption, as whenever I
have previously backed up the system it has been plain sailing to get
it back in again. But that was in SQL 7.
I shall get another backup (500 Km away!), unless you can advise more.
|||It might be that the actual backup spans multiple files, even though you
have only one of the members. You can see if this is your situation by
examining FamilyCount of the RESTORE LABELONLY results:
RESTORE LABELONLY
FROM DISK='C:\Backups\MyDatabase.bak'
Hope this helps.
Dan Guzman
SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132774484.545986.59230@.o13g2000cwo.googlegro ups.com...
> Geoff, thanks
> No, this was not the case. The database backup file was created in SQL
> Server 7 (SP4) and zips to 2MB after backup.
> On selection of the database file it's backup set properties can be
> seen. I selected to restore All, and there is no existing database over
> which it will overwrite. So it is hard to see why it should be asking
> for another file.
> Are there any other settings that can be changed? I am having a look...
> S.
>
|||The backup is striped. I never seen a case where SQL Server said it is, but it wasn't. Use RESTORE
LABELONLY as suggested by Dan, and you will see the number of members. I.e., you need to get the
other backup files, or a new non-striped backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132774484.545986.59230@.o13g2000cwo.googlegro ups.com...
> Geoff, thanks
> No, this was not the case. The database backup file was created in SQL
> Server 7 (SP4) and zips to 2MB after backup.
> On selection of the database file it's backup set properties can be
> seen. I selected to restore All, and there is no existing database over
> which it will overwrite. So it is hard to see why it should be asking
> for another file.
> Are there any other settings that can be changed? I am having a look...
> S.
>

HELP! Restore SQL7 database to SQL2000 SP3a problem

I have a small database that urgently needs restoring under SQL 2000.
SP3a is installed.
Is there a procedure?Yes.
First obtain three chickens and a mule...
Seriously, a SQL 7.0 database can be restored (or attached after detach) to
a SQL 2000 instance using the normal restore database commands or Enterprise
Manager. There is no difference in restoring a 7.0 backup to a SQL 2000
server than in restoring a SQL 2000 backup to a SQL 2000 server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132770162.841008.102880@.o13g2000cwo.googlegroups.com...
>I have a small database that urgently needs restoring under SQL 2000.
> SP3a is installed.
> Is there a procedure?
>|||You can use a RESTORE DATABASE command. For example:
RESTORE DATABASE MyDatabase
FROM DISK='C:\Backups\MyDatabase.bak'
WITH REPLACE
See the Books Online for details.
Hope this helps.
Dan Guzman
SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132770162.841008.102880@.o13g2000cwo.googlegroups.com...
>I have a small database that urgently needs restoring under SQL 2000.
> SP3a is installed.
> Is there a procedure?
>|||Thanks Geoff,
The error I am getting is:
SQL-DMO (ODBC SQLstate: 42000)
The media set for database (name) has 2 family members but only 1 are
provided. All members must be provided. Restore database is
terminating... "
S.|||Evidently your backup spanned multiple backup sets (files or tapes). You
need to specify all backup sets in a single restore command:
RESTORE DATABASE MySQL7Database
FROM C:\Backups\MySQL7Backup1.bak,C:\Backups\MySQL7Backup2.bak
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132773276.165857.173410@.z14g2000cwz.googlegroups.com...
> Thanks Geoff,
> The error I am getting is:
> SQL-DMO (ODBC SQLstate: 42000)
> The media set for database (name) has 2 family members but only 1 are
> provided. All members must be provided. Restore database is
> terminating... "
> S.
>|||Geoff, thanks
No, this was not the case. The database backup file was created in SQL
Server 7 (SP4) and zips to 2MB after backup.
On selection of the database file it's backup set properties can be
seen. I selected to restore All, and there is no existing database over
which it will overwrite. So it is hard to see why it should be asking
for another file.
Are there any other settings that can be changed? I am having a look...
S.|||Well guys, thanks very much anyway. I have tried using Dan Guzman's
suggestion of running a command script, but still no good - same error
type. I suppose that somehow there must be a corruption, as whenever I
have previously backed up the system it has been plain sailing to get
it back in again. But that was in SQL 7.
I shall get another backup (500 Km away!), unless you can advise more.|||It might be that the actual backup spans multiple files, even though you
have only one of the members. You can see if this is your situation by
examining FamilyCount of the RESTORE LABELONLY results:
RESTORE LABELONLY
FROM DISK='C:\Backups\MyDatabase.bak'
Hope this helps.
Dan Guzman
SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132774484.545986.59230@.o13g2000cwo.googlegroups.com...
> Geoff, thanks
> No, this was not the case. The database backup file was created in SQL
> Server 7 (SP4) and zips to 2MB after backup.
> On selection of the database file it's backup set properties can be
> seen. I selected to restore All, and there is no existing database over
> which it will overwrite. So it is hard to see why it should be asking
> for another file.
> Are there any other settings that can be changed? I am having a look...
> S.
>|||The backup is striped. I never seen a case where SQL Server said it is, but
it wasn't. Use RESTORE
LABELONLY as suggested by Dan, and you will see the number of members. I.e.,
you need to get the
other backup files, or a new non-striped backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132774484.545986.59230@.o13g2000cwo.googlegroups.com...
> Geoff, thanks
> No, this was not the case. The database backup file was created in SQL
> Server 7 (SP4) and zips to 2MB after backup.
> On selection of the database file it's backup set properties can be
> seen. I selected to restore All, and there is no existing database over
> which it will overwrite. So it is hard to see why it should be asking
> for another file.
> Are there any other settings that can be changed? I am having a look...
> S.
>

HELP! Restore SQL7 database to SQL2000 SP3a problem

I have a small database that urgently needs restoring under SQL 2000.
SP3a is installed.
Is there a procedure?Yes.
First obtain three chickens and a mule...
Seriously, a SQL 7.0 database can be restored (or attached after detach) to
a SQL 2000 instance using the normal restore database commands or Enterprise
Manager. There is no difference in restoring a 7.0 backup to a SQL 2000
server than in restoring a SQL 2000 backup to a SQL 2000 server.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132770162.841008.102880@.o13g2000cwo.googlegroups.com...
>I have a small database that urgently needs restoring under SQL 2000.
> SP3a is installed.
> Is there a procedure?
>|||You can use a RESTORE DATABASE command. For example:
RESTORE DATABASE MyDatabase
FROM DISK='C:\Backups\MyDatabase.bak'
WITH REPLACE
See the Books Online for details.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132770162.841008.102880@.o13g2000cwo.googlegroups.com...
>I have a small database that urgently needs restoring under SQL 2000.
> SP3a is installed.
> Is there a procedure?
>|||Thanks Geoff,
The error I am getting is:
SQL-DMO (ODBC SQLstate: 42000)
The media set for database (name) has 2 family members but only 1 are
provided. All members must be provided. Restore database is
terminating... "
S.|||Evidently your backup spanned multiple backup sets (files or tapes). You
need to specify all backup sets in a single restore command:
RESTORE DATABASE MySQL7Database
FROM C:\Backups\MySQL7Backup1.bak,C:\Backups\MySQL7Backup2.bak
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132773276.165857.173410@.z14g2000cwz.googlegroups.com...
> Thanks Geoff,
> The error I am getting is:
> SQL-DMO (ODBC SQLstate: 42000)
> The media set for database (name) has 2 family members but only 1 are
> provided. All members must be provided. Restore database is
> terminating... "
> S.
>|||Geoff, thanks
No, this was not the case. The database backup file was created in SQL
Server 7 (SP4) and zips to 2MB after backup.
On selection of the database file it's backup set properties can be
seen. I selected to restore All, and there is no existing database over
which it will overwrite. So it is hard to see why it should be asking
for another file.
Are there any other settings that can be changed? I am having a look...
S.|||Well guys, thanks very much anyway. I have tried using Dan Guzman's
suggestion of running a command script, but still no good - same error
type. I suppose that somehow there must be a corruption, as whenever I
have previously backed up the system it has been plain sailing to get
it back in again. But that was in SQL 7.
I shall get another backup (500 Km away!), unless you can advise more.|||It might be that the actual backup spans multiple files, even though you
have only one of the members. You can see if this is your situation by
examining FamilyCount of the RESTORE LABELONLY results:
RESTORE LABELONLY
FROM DISK='C:\Backups\MyDatabase.bak'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132774484.545986.59230@.o13g2000cwo.googlegroups.com...
> Geoff, thanks
> No, this was not the case. The database backup file was created in SQL
> Server 7 (SP4) and zips to 2MB after backup.
> On selection of the database file it's backup set properties can be
> seen. I selected to restore All, and there is no existing database over
> which it will overwrite. So it is hard to see why it should be asking
> for another file.
> Are there any other settings that can be changed? I am having a look...
> S.
>|||The backup is striped. I never seen a case where SQL Server said it is, but it wasn't. Use RESTORE
LABELONLY as suggested by Dan, and you will see the number of members. I.e., you need to get the
other backup files, or a new non-striped backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"proverbs3" <seumas.maclaren@.atkinsglobal.com> wrote in message
news:1132774484.545986.59230@.o13g2000cwo.googlegroups.com...
> Geoff, thanks
> No, this was not the case. The database backup file was created in SQL
> Server 7 (SP4) and zips to 2MB after backup.
> On selection of the database file it's backup set properties can be
> seen. I selected to restore All, and there is no existing database over
> which it will overwrite. So it is hard to see why it should be asking
> for another file.
> Are there any other settings that can be changed? I am having a look...
> S.
>sql

HELP! Non-Replicated DB thinks its a Publisher

I hosed myself, please help me somebody.

We have a development server (SQL7) where the database is a restored copy of
production (where we use replication, but not in the development
environment).

While we rebuild the server recently (so we could move off of NT onto 2000),
everything looked to be working fine.

But I recently, messed up and did a massive update filling the transaction
log of the development server. Now I can't update data in development.

I tried to do my usual:

BACKUP LOG LAMS WITH Truncate_only

only to get a message:

The log was not truncated because records at the beginning of the log are
pending replication. Ensure the Log Reader Agent is running or use
sp_repldone to mark transactions as distributed.

Did a little research into BOL and tried to call the following two procs:

exec sp_repldone
@.xactid = null ,
@.xact_seqno = null ,
@.reset = 1

exec sp_repltrans

Both of which gave me an error of :
The database is not published.

Which it isn't as we don't run replication in the development environment.

I stopped and restarted the SQL Service (as that has cleared issues in the
past), but didn't reboot the server.

How can I make the database not think It's replicated (or that its caught
up?).

I was thinking, would I be even be able to do another restore of a more
recent copy of Production?

Sincerely ...
Depressed in DelawareNever Mind, I restored development from a more recent copy of production.

Is there a command to fix a SQL 7 DB when it gets confused about
replication?

"David Rawheiser" <rawhide58@.hotmail.com> wrote in message
news:DD3Bd.1194718$Gx4.69619@.bgtnsc04-news.ops.worldnet.att.net...
>I hosed myself, please help me somebody.
> We have a development server (SQL7) where the database is a restored copy
> of production (where we use replication, but not in the development
> environment).
> While we rebuild the server recently (so we could move off of NT onto
> 2000), everything looked to be working fine.
> But I recently, messed up and did a massive update filling the transaction
> log of the development server. Now I can't update data in development.
> I tried to do my usual:
> BACKUP LOG LAMS WITH Truncate_only
> only to get a message:
> The log was not truncated because records at the beginning of the log are
> pending replication. Ensure the Log Reader Agent is running or use
> sp_repldone to mark transactions as distributed.
> Did a little research into BOL and tried to call the following two procs:
> exec sp_repldone
> @.xactid = null ,
> @.xact_seqno = null ,
> @.reset = 1
> exec sp_repltrans
> Both of which gave me an error of :
> The database is not published.
> Which it isn't as we don't run replication in the development environment.
> I stopped and restarted the SQL Service (as that has cleared issues in the
> past), but didn't reboot the server.
> How can I make the database not think It's replicated (or that its caught
> up?).
> I was thinking, would I be even be able to do another restore of a more
> recent copy of Production?
> Sincerely ...
> Depressed in Delaware

Help! Can't pass names with apostrophe from ASP to SQL7 proc

I have a proc that does wildcard searches on names which works fine
expect with names that contain an apostrophe like O'Neil.
When O'Neil is sent to the proc, I get "Incorrect syntax near 'Neil'."
This tells me I've got a delimiter issue.
I've tried replacing the single apostrophe with a double or even using
quotes as the delimiter and still get an error. What should I try; can
anyone help?
BTW, here's an example of the proc.
========================================
=============
CREATE proc getName
@.CUSTNAME varchar(15)
as
declare @.SQL varchar(4000)
set @.SQL = 'select PARENT_NAME, CITY, STATE, ZIP from
[CS-170].CUST.dbo.CUST_ADR
where
PARENT_NAME like ''%' + @.CUSTNAME + '%'''
exec (@.SQL)
========================================
==============
I've passed the name as below and still get errors.
getName O'Neil
getName 'O'Neil'
getName ''O'Neil'' - All Single quotes chr (39)
getName "O'Neil" - Quotes on the outside chr(34)
getName 'O''Neil' - All Single quotes chr (39)
getName "O''Neil" - Quotes on the outside chr(34), and double
singles in the name chr(39)
Nothing works due to the syntex. What can I do, please HELP!!
Thank you,
DaeI don't understand why you are using dynamic sql for this..
I guess you simplified the actual query for the post :)
But anyways.. try this.
getName 'O''''Neil' -- 4 single quotes|||this would work
getname 'o''''niel'
Best Regards
Vadivel
http://vadivel.blogspot.com
"Omnibuzz" wrote:

> I don't understand why you are using dynamic sql for this..
> I guess you simplified the actual query for the post :)
> But anyways.. try this.
> getName 'O''''Neil' -- 4 single quotes|||Or this should work:
SET QUOTED_IDENTIFIER OFF
EXEC getName "O'Anders"
"Vadivel" wrote:
> this would work
> getname 'o''''niel'
> Best Regards
> Vadivel
> http://vadivel.blogspot.com
>
> "Omnibuzz" wrote:
>