Hi all,
Okay, we've got a product which has SQL Server as the backend database.
The client has the product as well as the database.
But the DBA at the clients end messes up with the data & we are held
responsible (that the product is what is messing up the data & NOT their
DBA).
How can we prevent this,
ie. try to encrypt the database or restrict access to the database to the
DBA.
Also, another requirement is that we do NOT want them to see the DB
structures, the tables, the data in the Databse!!!!
options,
1. Get them to install a new instance of SQL Server & NOT give the DBA or
anyone the password & have the password embeded in the application (thus
only the application can access the SQL Database).
NOTE : THe product and the SQL Servers WILL have to be at the clients end.
any other options?
Hi
As you don't have the means to stop physical access this is difficult. You
may want to make sure that you are auditing such events. If you want to
carry out encryption then it is probably better on the client as the DBA
will have access to the methods used at the database end. You may also want
to look throught the products and articles on
http://www.sqlsecurity.com/DesktopDe...ndex=0&tabid=1
John
"D.Rudiani" <rudi@.www.com> wrote in message
news:ervb1anWFHA.1796@.TK2MSFTNGP15.phx.gbl...
> Hi all,
> Okay, we've got a product which has SQL Server as the backend database.
> The client has the product as well as the database.
> But the DBA at the clients end messes up with the data & we are held
> responsible (that the product is what is messing up the data & NOT their
> DBA).
> How can we prevent this,
> ie. try to encrypt the database or restrict access to the database to the
> DBA.
> Also, another requirement is that we do NOT want them to see the DB
> structures, the tables, the data in the Databse!!!!
> options,
> 1. Get them to install a new instance of SQL Server & NOT give the DBA or
> anyone the password & have the password embeded in the application (thus
> only the application can access the SQL Database).
> NOTE : THe product and the SQL Servers WILL have to be at the clients end.
> any other options?
>
Showing posts with label client. Show all posts
Showing posts with label client. Show all posts
Wednesday, March 28, 2012
restrict access to a database
Hi all,
Okay, we've got a product which has SQL Server as the backend database.
The client has the product as well as the database.
But the DBA at the clients end messes up with the data & we are held
responsible (that the product is what is messing up the data & NOT their
DBA).
How can we prevent this,
ie. try to encrypt the database or restrict access to the database to the
DBA.
Also, another requirement is that we do NOT want them to see the DB
structures, the tables, the data in the Databse!!!!
options,
1. Get them to install a new instance of SQL Server & NOT give the DBA or
anyone the password & have the password embeded in the application (thus
only the application can access the SQL Database).
NOTE : THe product and the SQL Servers WILL have to be at the clients end.
any other options?Do you intend to manage that server 100%? In other words you will be solely
and entirely responsible for monitoring, security, backups, performance,
maintenance and troubleshooting to an agreed SLA? If the answer is yes, then
of course you could in principle lock down the server and deny user access
to the database (I'm assuming that you used stored procs as your data access
tier so that you can deny object-level permissions to users).
If you can't answer yes to all of the above then the client has a legitimate
need to manage the database themselves and IMO you cannot reasonably deny
them sy
min level access and you cannot and should not attempt to secure
your system from the DBA. It seems to me that your best course of action in
that case would be to come to an agreement with the customer about the
division of responsibilities for the system and maybe implement some logging
process so that you have an audit trail of what has occurred to the data.
David Portas
SQL Server MVP
--|||wow!
how can i set object level permissions for users (including the DBA)?
& yes, we do have SPs.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Is-dnXwsyoLKoxTfRVn-vA@.giganews.com...
> Do you intend to manage that server 100%? In other words you will be
solely
> and entirely responsible for monitoring, security, backups, performance,
> maintenance and troubleshooting to an agreed SLA? If the answer is yes,
then
> of course you could in principle lock down the server and deny user access
> to the database (I'm assuming that you used stored procs as your data
access
> tier so that you can deny object-level permissions to users).
> If you can't answer yes to all of the above then the client has a
legitimate
> need to manage the database themselves and IMO you cannot reasonably deny
> them symin level access and you cannot and should not attempt to secure
> your system from the DBA. It seems to me that your best course of action
in
> that case would be to come to an agreement with the customer about the
> division of responsibilities for the system and maybe implement some
logging
> process so that you have an audit trail of what has occurred to the data.
> --
> David Portas
> SQL Server MVP
> --
>|||EXEC sp_addrolemember 'db_denydatawriter', 'user name'
EXEC sp_addrolemember 'db_denydatareader', 'user name'
GRANT EXECUTE TO user_name ON usp_proc_name
David Portas
SQL Server MVP
--
Okay, we've got a product which has SQL Server as the backend database.
The client has the product as well as the database.
But the DBA at the clients end messes up with the data & we are held
responsible (that the product is what is messing up the data & NOT their
DBA).
How can we prevent this,
ie. try to encrypt the database or restrict access to the database to the
DBA.
Also, another requirement is that we do NOT want them to see the DB
structures, the tables, the data in the Databse!!!!
options,
1. Get them to install a new instance of SQL Server & NOT give the DBA or
anyone the password & have the password embeded in the application (thus
only the application can access the SQL Database).
NOTE : THe product and the SQL Servers WILL have to be at the clients end.
any other options?Do you intend to manage that server 100%? In other words you will be solely
and entirely responsible for monitoring, security, backups, performance,
maintenance and troubleshooting to an agreed SLA? If the answer is yes, then
of course you could in principle lock down the server and deny user access
to the database (I'm assuming that you used stored procs as your data access
tier so that you can deny object-level permissions to users).
If you can't answer yes to all of the above then the client has a legitimate
need to manage the database themselves and IMO you cannot reasonably deny
them sy
min level access and you cannot and should not attempt to secureyour system from the DBA. It seems to me that your best course of action in
that case would be to come to an agreement with the customer about the
division of responsibilities for the system and maybe implement some logging
process so that you have an audit trail of what has occurred to the data.
David Portas
SQL Server MVP
--|||wow!
how can i set object level permissions for users (including the DBA)?
& yes, we do have SPs.
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:Is-dnXwsyoLKoxTfRVn-vA@.giganews.com...
> Do you intend to manage that server 100%? In other words you will be
solely
> and entirely responsible for monitoring, security, backups, performance,
> maintenance and troubleshooting to an agreed SLA? If the answer is yes,
then
> of course you could in principle lock down the server and deny user access
> to the database (I'm assuming that you used stored procs as your data
access
> tier so that you can deny object-level permissions to users).
> If you can't answer yes to all of the above then the client has a
legitimate
> need to manage the database themselves and IMO you cannot reasonably deny
> them sy
min level access and you cannot and should not attempt to secure> your system from the DBA. It seems to me that your best course of action
in
> that case would be to come to an agreement with the customer about the
> division of responsibilities for the system and maybe implement some
logging
> process so that you have an audit trail of what has occurred to the data.
> --
> David Portas
> SQL Server MVP
> --
>|||EXEC sp_addrolemember 'db_denydatawriter', 'user name'
EXEC sp_addrolemember 'db_denydatareader', 'user name'
GRANT EXECUTE TO user_name ON usp_proc_name
David Portas
SQL Server MVP
--
restrict access to a database
Hi all,
Okay, we've got a product which has SQL Server as the backend database.
The client has the product as well as the database.
But the DBA at the clients end messes up with the data & we are held
responsible (that the product is what is messing up the data & NOT their
DBA).
How can we prevent this,
ie. try to encrypt the database or restrict access to the database to the
DBA.
Also, another requirement is that we do NOT want them to see the DB
structures, the tables, the data in the Databse!!!!
options,
1. Get them to install a new instance of SQL Server & NOT give the DBA or
anyone the password & have the password embeded in the application (thus
only the application can access the SQL Database).
NOTE : THe product and the SQL Servers WILL have to be at the clients end.
any other options?D.Rudiani
If you want to restict access to the database then remove him/her from
sysadmin server role and don't grant the access to the database
"D.Rudiani" <rudi@.www.com> wrote in message
news:%23dJk2anWFHA.2448@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> Okay, we've got a product which has SQL Server as the backend database.
> The client has the product as well as the database.
> But the DBA at the clients end messes up with the data & we are held
> responsible (that the product is what is messing up the data & NOT their
> DBA).
> How can we prevent this,
> ie. try to encrypt the database or restrict access to the database to the
> DBA.
> Also, another requirement is that we do NOT want them to see the DB
> structures, the tables, the data in the Databse!!!!
> options,
> 1. Get them to install a new instance of SQL Server & NOT give the DBA or
> anyone the password & have the password embeded in the application (thus
> only the application can access the SQL Database).
> NOTE : THe product and the SQL Servers WILL have to be at the clients end.
> any other options?
>|||Hi,
Since the SQL SERVER machine is in the clients place and DBA needs to
perform administrative tasks ( BACKUP , RECOVERY , DBCC, REINDEX..),
it is very difficult to restrict the DBA. Only way to restrict is change the
OS Level admin password and SA password for sql server and do not hand it to
client side DBA. In this case he can not perform any administrative tasks.
Also, another requirement is that we do NOT want them to see the DB
structures, the tables, the data in the Databse!!!!
See Application roles in Books online.
Thanks
Hari
SQL Server MVP
"D.Rudiani" <rudi@.www.com> wrote in message
news:%23dJk2anWFHA.2448@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> Okay, we've got a product which has SQL Server as the backend database.
> The client has the product as well as the database.
> But the DBA at the clients end messes up with the data & we are held
> responsible (that the product is what is messing up the data & NOT their
> DBA).
> How can we prevent this,
> ie. try to encrypt the database or restrict access to the database to the
> DBA.
> Also, another requirement is that we do NOT want them to see the DB
> structures, the tables, the data in the Databse!!!!
> options,
> 1. Get them to install a new instance of SQL Server & NOT give the DBA or
> anyone the password & have the password embeded in the application (thus
> only the application can access the SQL Database).
> NOTE : THe product and the SQL Servers WILL have to be at the clients end.
> any other options?
>sql
Okay, we've got a product which has SQL Server as the backend database.
The client has the product as well as the database.
But the DBA at the clients end messes up with the data & we are held
responsible (that the product is what is messing up the data & NOT their
DBA).
How can we prevent this,
ie. try to encrypt the database or restrict access to the database to the
DBA.
Also, another requirement is that we do NOT want them to see the DB
structures, the tables, the data in the Databse!!!!
options,
1. Get them to install a new instance of SQL Server & NOT give the DBA or
anyone the password & have the password embeded in the application (thus
only the application can access the SQL Database).
NOTE : THe product and the SQL Servers WILL have to be at the clients end.
any other options?D.Rudiani
If you want to restict access to the database then remove him/her from
sysadmin server role and don't grant the access to the database
"D.Rudiani" <rudi@.www.com> wrote in message
news:%23dJk2anWFHA.2448@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> Okay, we've got a product which has SQL Server as the backend database.
> The client has the product as well as the database.
> But the DBA at the clients end messes up with the data & we are held
> responsible (that the product is what is messing up the data & NOT their
> DBA).
> How can we prevent this,
> ie. try to encrypt the database or restrict access to the database to the
> DBA.
> Also, another requirement is that we do NOT want them to see the DB
> structures, the tables, the data in the Databse!!!!
> options,
> 1. Get them to install a new instance of SQL Server & NOT give the DBA or
> anyone the password & have the password embeded in the application (thus
> only the application can access the SQL Database).
> NOTE : THe product and the SQL Servers WILL have to be at the clients end.
> any other options?
>|||Hi,
Since the SQL SERVER machine is in the clients place and DBA needs to
perform administrative tasks ( BACKUP , RECOVERY , DBCC, REINDEX..),
it is very difficult to restrict the DBA. Only way to restrict is change the
OS Level admin password and SA password for sql server and do not hand it to
client side DBA. In this case he can not perform any administrative tasks.
Also, another requirement is that we do NOT want them to see the DB
structures, the tables, the data in the Databse!!!!
See Application roles in Books online.
Thanks
Hari
SQL Server MVP
"D.Rudiani" <rudi@.www.com> wrote in message
news:%23dJk2anWFHA.2448@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> Okay, we've got a product which has SQL Server as the backend database.
> The client has the product as well as the database.
> But the DBA at the clients end messes up with the data & we are held
> responsible (that the product is what is messing up the data & NOT their
> DBA).
> How can we prevent this,
> ie. try to encrypt the database or restrict access to the database to the
> DBA.
> Also, another requirement is that we do NOT want them to see the DB
> structures, the tables, the data in the Databse!!!!
> options,
> 1. Get them to install a new instance of SQL Server & NOT give the DBA or
> anyone the password & have the password embeded in the application (thus
> only the application can access the SQL Database).
> NOTE : THe product and the SQL Servers WILL have to be at the clients end.
> any other options?
>sql
Friday, March 23, 2012
Restoring SQL Server 6.5 .DAT file to SQL 2000
All,
My client has give me a 6.5 backup file in a .DAT format.
I want to restore it in SQL2000.
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
You cannot restore it to SQL 2k.
You can only restore it (painfully) to a 6.5 system and then perform
upgrades on it.
Rick Sawtell
MCT, MCSD, MCDBA
|||No can do. You will have to build a SQL 6.5 server, restore the file, then
convert to 7.0/2000. Without the sysdevices, sysdatabases, and sysusages
information, you cannot restore a SQL 6.5 database. Unlike SQL 7.0 and
higher, SQL 6.5 database backups are not self-describing.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
|||Hi,
SQL 6.5 and SQL 2000 architecture is different and since the backup restore
is not allowed. So only possibility is:-
1. Restore the 6.5 backup DAT file into SQL 6.5 machine
2. INstall SQL 2000 and service pack
3. Use Upgrade wizard rto upgrade the SQL 6.5 database to SQL 2000
4. Upgrade wizard will copy all the data / objects to SQL 2000.
Note:-
Execute a DBCC and update statistics before the upgrade
Thanks
Hari
SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
|||In addition to the other posts:
You *might* be able to restore your 6.5 backup on another 6.5 machine even if you don't know the
database fragments (master..sysusages etc). But you will end up with data pages where SQL Server
expects log pages and vice versa. For data pages where SQL Server expects log pages, DBCC NEWALLOG
will return 2558 errors (I believe) and you have to physically move the data. Possibly create script
and transfer all over to a new database. Possibly by rebuilding all indexes. Not to be taken lightly
if you don't have good 6.5 expertise.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
|||Thanks every one for taking time to reply :-)
Regards
Amit
"Amit" wrote:
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
My client has give me a 6.5 backup file in a .DAT format.
I want to restore it in SQL2000.
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
You cannot restore it to SQL 2k.
You can only restore it (painfully) to a 6.5 system and then perform
upgrades on it.
Rick Sawtell
MCT, MCSD, MCDBA
|||No can do. You will have to build a SQL 6.5 server, restore the file, then
convert to 7.0/2000. Without the sysdevices, sysdatabases, and sysusages
information, you cannot restore a SQL 6.5 database. Unlike SQL 7.0 and
higher, SQL 6.5 database backups are not self-describing.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
|||Hi,
SQL 6.5 and SQL 2000 architecture is different and since the backup restore
is not allowed. So only possibility is:-
1. Restore the 6.5 backup DAT file into SQL 6.5 machine
2. INstall SQL 2000 and service pack
3. Use Upgrade wizard rto upgrade the SQL 6.5 database to SQL 2000
4. Upgrade wizard will copy all the data / objects to SQL 2000.
Note:-
Execute a DBCC and update statistics before the upgrade
Thanks
Hari
SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
|||In addition to the other posts:
You *might* be able to restore your 6.5 backup on another 6.5 machine even if you don't know the
database fragments (master..sysusages etc). But you will end up with data pages where SQL Server
expects log pages and vice versa. For data pages where SQL Server expects log pages, DBCC NEWALLOG
will return 2558 errors (I believe) and you have to physically move the data. Possibly create script
and transfer all over to a new database. Possibly by rebuilding all indexes. Not to be taken lightly
if you don't have good 6.5 expertise.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
|||Thanks every one for taking time to reply :-)
Regards
Amit
"Amit" wrote:
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
Restoring SQL Server 6.5 .DAT file to SQL 2000
All,
My client has give me a 6.5 backup file in a .DAT format.
I want to restore it in SQL2000."Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
You cannot restore it to SQL 2k.
You can only restore it (painfully) to a 6.5 system and then perform
upgrades on it.
Rick Sawtell
MCT, MCSD, MCDBA|||No can do. You will have to build a SQL 6.5 server, restore the file, then
convert to 7.0/2000. Without the sysdevices, sysdatabases, and sysusages
information, you cannot restore a SQL 6.5 database. Unlike SQL 7.0 and
higher, SQL 6.5 database backups are not self-describing.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Hi,
SQL 6.5 and SQL 2000 architecture is different and since the backup restore
is not allowed. So only possibility is:-
1. Restore the 6.5 backup DAT file into SQL 6.5 machine
2. INstall SQL 2000 and service pack
3. Use Upgrade wizard rto upgrade the SQL 6.5 database to SQL 2000
4. Upgrade wizard will copy all the data / objects to SQL 2000.
Note:-
Execute a DBCC and update statistics before the upgrade
Thanks
Hari
SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||In addition to the other posts:
You *might* be able to restore your 6.5 backup on another 6.5 machine even if you don't know the
database fragments (master..sysusages etc). But you will end up with data pages where SQL Server
expects log pages and vice versa. For data pages where SQL Server expects log pages, DBCC NEWALLOG
will return 2558 errors (I believe) and you have to physically move the data. Possibly create script
and transfer all over to a new database. Possibly by rebuilding all indexes. Not to be taken lightly
if you don't have good 6.5 expertise.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Thanks every one for taking time to reply :-)
Regards
Amit
"Amit" wrote:
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
My client has give me a 6.5 backup file in a .DAT format.
I want to restore it in SQL2000."Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
You cannot restore it to SQL 2k.
You can only restore it (painfully) to a 6.5 system and then perform
upgrades on it.
Rick Sawtell
MCT, MCSD, MCDBA|||No can do. You will have to build a SQL 6.5 server, restore the file, then
convert to 7.0/2000. Without the sysdevices, sysdatabases, and sysusages
information, you cannot restore a SQL 6.5 database. Unlike SQL 7.0 and
higher, SQL 6.5 database backups are not self-describing.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Hi,
SQL 6.5 and SQL 2000 architecture is different and since the backup restore
is not allowed. So only possibility is:-
1. Restore the 6.5 backup DAT file into SQL 6.5 machine
2. INstall SQL 2000 and service pack
3. Use Upgrade wizard rto upgrade the SQL 6.5 database to SQL 2000
4. Upgrade wizard will copy all the data / objects to SQL 2000.
Note:-
Execute a DBCC and update statistics before the upgrade
Thanks
Hari
SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||In addition to the other posts:
You *might* be able to restore your 6.5 backup on another 6.5 machine even if you don't know the
database fragments (master..sysusages etc). But you will end up with data pages where SQL Server
expects log pages and vice versa. For data pages where SQL Server expects log pages, DBCC NEWALLOG
will return 2558 errors (I believe) and you have to physically move the data. Possibly create script
and transfer all over to a new database. Possibly by rebuilding all indexes. Not to be taken lightly
if you don't have good 6.5 expertise.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Thanks every one for taking time to reply :-)
Regards
Amit
"Amit" wrote:
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
Restoring SQL Server 6.5 .DAT file to SQL 2000
All,
My client has give me a 6.5 backup file in a .DAT format.
I want to restore it in SQL2000."Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
You cannot restore it to SQL 2k.
You can only restore it (painfully) to a 6.5 system and then perform
upgrades on it.
Rick Sawtell
MCT, MCSD, MCDBA|||No can do. You will have to build a SQL 6.5 server, restore the file, then
convert to 7.0/2000. Without the sysdevices, sysdatabases, and sysusages
information, you cannot restore a SQL 6.5 database. Unlike SQL 7.0 and
higher, SQL 6.5 database backups are not self-describing.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Hi,
SQL 6.5 and SQL 2000 architecture is different and since the backup restore
is not allowed. So only possibility is:-
1. Restore the 6.5 backup DAT file into SQL 6.5 machine
2. INstall SQL 2000 and service pack
3. Use Upgrade wizard rto upgrade the SQL 6.5 database to SQL 2000
4. Upgrade wizard will copy all the data / objects to SQL 2000.
Note:-
Execute a DBCC and update statistics before the upgrade
Thanks
Hari
SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||In addition to the other posts:
You *might* be able to restore your 6.5 backup on another 6.5 machine even i
f you don't know the
database fragments (master..sysusages etc). But you will end up with data pa
ges where SQL Server
expects log pages and vice versa. For data pages where SQL Server expects lo
g pages, DBCC NEWALLOG
will return 2558 errors (I believe) and you have to physically move the data
. Possibly create script
and transfer all over to a new database. Possibly by rebuilding all indexes.
Not to be taken lightly
if you don't have good 6.5 expertise.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Thanks every one for taking time to reply :-)
Regards
Amit
"Amit" wrote:
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
My client has give me a 6.5 backup file in a .DAT format.
I want to restore it in SQL2000."Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
You cannot restore it to SQL 2k.
You can only restore it (painfully) to a 6.5 system and then perform
upgrades on it.
Rick Sawtell
MCT, MCSD, MCDBA|||No can do. You will have to build a SQL 6.5 server, restore the file, then
convert to 7.0/2000. Without the sysdevices, sysdatabases, and sysusages
information, you cannot restore a SQL 6.5 database. Unlike SQL 7.0 and
higher, SQL 6.5 database backups are not self-describing.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Hi,
SQL 6.5 and SQL 2000 architecture is different and since the backup restore
is not allowed. So only possibility is:-
1. Restore the 6.5 backup DAT file into SQL 6.5 machine
2. INstall SQL 2000 and service pack
3. Use Upgrade wizard rto upgrade the SQL 6.5 database to SQL 2000
4. Upgrade wizard will copy all the data / objects to SQL 2000.
Note:-
Execute a DBCC and update statistics before the upgrade
Thanks
Hari
SQL Server MVP
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||In addition to the other posts:
You *might* be able to restore your 6.5 backup on another 6.5 machine even i
f you don't know the
database fragments (master..sysusages etc). But you will end up with data pa
ges where SQL Server
expects log pages and vice versa. For data pages where SQL Server expects lo
g pages, DBCC NEWALLOG
will return 2558 errors (I believe) and you have to physically move the data
. Possibly create script
and transfer all over to a new database. Possibly by rebuilding all indexes.
Not to be taken lightly
if you don't have good 6.5 expertise.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:E15A0D61-F208-4FC8-B7A4-53A7461B24EA@.microsoft.com...
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>|||Thanks every one for taking time to reply :-)
Regards
Amit
"Amit" wrote:
> All,
> My client has give me a 6.5 backup file in a .DAT format.
> I want to restore it in SQL2000.
>
Tuesday, March 20, 2012
Restoring Multiple Logs In One Operation
I am working with a client on backup strategy. Their database undergoes a
full backup 2-3 times a week with hourly log backups during business hours
(8:00-5:00). When doing a restore, there are 10-15 log files with a TRN
extension that I need to restore one by one. Is there a way to restore the
logs as a group?
--
Larry Menzin
American Techsystems Corp.Not without executing several RESTORE LOG commands. You can automate this by writing some code for
your client. Hard to give further recommendations as we don't know anything about how the backups
are taken, named etc. But using the backup history tables in msdb is what EM does.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:CDDCDA6F-255D-4069-99C5-C10637DDD4EE@.microsoft.com...
>I am working with a client on backup strategy. Their database undergoes a
> full backup 2-3 times a week with hourly log backups during business hours
> (8:00-5:00). When doing a restore, there are 10-15 log files with a TRN
> extension that I need to restore one by one. Is there a way to restore the
> logs as a group?
> --
> Larry Menzin
> American Techsystems Corp.
full backup 2-3 times a week with hourly log backups during business hours
(8:00-5:00). When doing a restore, there are 10-15 log files with a TRN
extension that I need to restore one by one. Is there a way to restore the
logs as a group?
--
Larry Menzin
American Techsystems Corp.Not without executing several RESTORE LOG commands. You can automate this by writing some code for
your client. Hard to give further recommendations as we don't know anything about how the backups
are taken, named etc. But using the backup history tables in msdb is what EM does.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Larry Menzin" <LarryMenzin@.discussions.microsoft.com> wrote in message
news:CDDCDA6F-255D-4069-99C5-C10637DDD4EE@.microsoft.com...
>I am working with a client on backup strategy. Their database undergoes a
> full backup 2-3 times a week with hourly log backups during business hours
> (8:00-5:00). When doing a restore, there are 10-15 log files with a TRN
> extension that I need to restore one by one. Is there a way to restore the
> logs as a group?
> --
> Larry Menzin
> American Techsystems Corp.
Friday, March 9, 2012
Restoring Linux ANSI_SQL to SQL 2005
Our firm needs to analyze some financial data for a client. They gave us a SQL database file in ANSI format. Is there a way to import this data into SQL 2005?
Thanks,
Steve
If the data is in a 'standard' format, and If you have a good data map, then you 'should' be able to use SSIS, or the IMPORT Wizard, to import the data into a functioning SQL Server.|||Arnie,
Thanks for the reply. Do I need to contact the client to get column types and widths, etc?
Steve
|||I would definitely want some way to undertand what data is in the data file, and how it is organized. So that sounds like a good plan. -Unless you can open the datafile and inspect the format.Saturday, February 25, 2012
Restoring datbase on different machine
Hi All,
I am using SQL serve 2000. My client has sent me one database. I want to restore here. How do I restore the database which has been sent to me.
Vinihi vini,
what do u mean by the client has sent u a database? I mean is it a database backup or the database file(mdf)??
If it is a backup of the database then you can create a empty database and restore the database backup on this new database.
If it is a database file (mdf) then attach the database to the database server.
regards,
harsh.|||To restore a dump from other Server , you don't have to create an empty database !! Use RESTORE COMMAND WITH MOVE option (See BOL) or USe Enterprise manager , Right click any existing database : Click Restore : Change the name to New Db , In Options tab , amke sure the Physical File Path is Correct matching to the Server you are restoring , Click Force Restore and Hit OK .
For MDF Files If you do not have Log File with it , sp_Attach_singly_file might work but you are likely to loose the transactions which are uncommited and sitting on MDF file ..
I am using SQL serve 2000. My client has sent me one database. I want to restore here. How do I restore the database which has been sent to me.
Vinihi vini,
what do u mean by the client has sent u a database? I mean is it a database backup or the database file(mdf)??
If it is a backup of the database then you can create a empty database and restore the database backup on this new database.
If it is a database file (mdf) then attach the database to the database server.
regards,
harsh.|||To restore a dump from other Server , you don't have to create an empty database !! Use RESTORE COMMAND WITH MOVE option (See BOL) or USe Enterprise manager , Right click any existing database : Click Restore : Change the name to New Db , In Options tab , amke sure the Physical File Path is Correct matching to the Server you are restoring , Click Force Restore and Hit OK .
For MDF Files If you do not have Log File with it , sp_Attach_singly_file might work but you are likely to loose the transactions which are uncommited and sitting on MDF file ..
Subscribe to:
Posts (Atom)