microsoft sql server 2000

i wanted to restore user DB from one sql server to another sql server ,
one database is having so many table and have user called digi
he is created so many SP and some tables., when i restore the db it
restored without any problem.,

after restoring application is not working

how to ensure that restored DB is having same security as the original
for that user .

when i tried to run the script of that db over that restored DB

it was showing user digi does not exist. but i have creted user digi

where can i get the useful information about this

/sreeni

--
srin

Posted via http://dbforums.comUytkownik "sreenivasa" <member32738@.dbforums.com> napisa w wiadomoci
news:3084542.1057641115@.dbforums.com...
> i wanted to restore user DB from one sql server to another sql server ,
<cut>
It's probably your answer - another sql so it means another master database.
You have user account in database wich was restored, but you do not have
user login (in master database - sysusers table) wich is connected to
database account.
You must drop database user and create new login - not recomended, or use
sp_change_users_login with Auto_Fix option.
regards
Marcin D

Microsoft S1-DMO(ODBC SQL State:42000)

The bacend-up database has on-disk structure version 539.The server supports version 515 and cannot restore or upgrade this database.Originally posted by maheedhar
The bacend-up database has on-disk structure version 539.The server supports version 515 and cannot restore or upgrade this database.|||Ensure the source and target SQL server's version & collation settings are similar.

If not you can use DTS to import/export the data alone.

messages aren't getting through after backup / restore on a different server...

after restoring a database and regenerating keys, I'm trying to queue messages, and they're all hanging out in sys.transmission_queue with the following message:
An exception occurred while enqueueing a message in the target queue. Error: 15517, State: 1. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.

I can't find any documentation or blog info on this error... Help!

thanks!Have you set your database to trustworty?

ALTER DATABASE db_name
SET TRUSTWORTHY ON

Also, maje sure you have a master key in both databases.

CREATE DATABASE MASTER KEY
ENCRYPTION BY PASSWORD = 'somePassW0rd1'

Please let us know if this helps

Niels|||hi Niels.

Nope, the SET TRUSTWORTHY ON on the database did not work.

It would probably be helpful if I mentioned that the backup was taken on the April CTP server, and the restore on the September version...

also - both the initiator and target queues live in the same database...

|||

Which server principal (i.e. login) owns the restored database? Has anything changed with the SQL instance or Windows users since backup was taken? For example you are trying to restore on a machine not connected to a domain and the server principal owning the database was a domain user?

Later,
Rushi

|||Rushi -- a domain administrator owns both databases.
Both servers are connected to the domain, and all services are also run by the domain administrator.|||Probably the dbo of the database is the original login that created the database, on the original server, and that login cannot be impersonated on the new server (e.g. the login is the Windows login corresponding to the original server Administrator account).
Use ALTER AUTHORIZATION ON DATABASE <dbname> TO <loginname> to change the owner of the database to a new login (e.g. [sa]), it will change the dbo to map to a login than is OK to be impersonated.

HTH,
~ Remus|||thanks Remus -- that solved the problem.