-----------------------------------------------------------
New Message on BDOTNET
-----------------------------------------------------------
From: VinodK [TLabs, SCT]
Message 7 in Discussion
Hi Ravi, Well this seems to be an interesting requirement ... But from the
description you have mentioned and the way thread has moved I did have a couple of
points to add ... 1. If your HDD craches is the assumption you have made makes it
impossible for all the information in all the other databases not available ... Hence
it would be advisable to take a backup of all the kwy databases (master, MSDB) along
with your normal databases. 2. If you were also looking at transfering logins and
passwords between two different servers then there are a couple of ways .. I thought
this might also facinate you ... Try using DTS for this activity as a) Connect
to the SQL Server 2000 destination server, move to to the Data Transformation Services
in SQL Server Enterprise Manager, expand the folder, right-click Local Packages, and
then click New Package.
b) After the DTS package designer opens, click Transfer Logins Task on the Task
menu. Complete the information about the Source, Destination and Logins tabs as
appropriate. If you are importing logins from an instance of SQL Server that is on a
separate computer, your instance of SQL Server will must be running under a Domain
Account to complete the task. And a couple of footnotes before you start using the
master backup on your server ... The master database contains server-wide information,
and affects all databases on the server. By restoring the master database, you may
encounter additional user IDs and/or databases that are lost or have incorrect
permissions. Any changes to the master that have occurred since the time of the backup
will be lost. Only use this method if you are certain that the backup version of the
master database contains accurate information for the user database in question and
all other databases on the server ... Basically if I were to analyze what happens
behind the scenes ... Restoring a dump of the master database from the time of the
user database dump to the server before loading the user database. Doing this ensures
that all user information in the user database matches correctly with the syslogins
table in master ... Hence all the links maintained between sysylogins, sysusers and
sysalternates are maintained ... It is to be understood that the normal information
about the user associated with the database in present in the normal database backup
itself .. What is missing is the definition of the user and this information is global
and is hence stored in the master database ... I hope I've made the concepts clear
... :) Regards, Vinod Kumar Microsoft India Community Star www.extremeexperts.com
-----------------------------------------------------------
To stop getting this e-mail, or change how often it arrives, go to your E-mail
Settings.
http://groups.msn.com/bdotnet/_emailsettings.msnw
Need help? If you've forgotten your password, please go to Passport Member Services.
http://groups.msn.com/_passportredir.msnw?ppmprop=help
For other questions or feedback, go to our Contact Us page.
http://groups.msn.com/contact
If you do not want to receive future e-mail from this MSN group, or if you received
this message by mistake, please click the "Remove" link below. On the pre-addressed
e-mail message that opens, simply click "Send". Your e-mail address will be deleted
from this group's mailing list.
mailto:[EMAIL PROTECTED]
