Showing posts with label log-in. Show all posts
Showing posts with label log-in. Show all posts

Monday, March 12, 2012

Log-In error

SQL Server does not exist or access denied!
Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data,even after
restart the computer. (does it means the sa password still correct?)
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer". Either with sa or Windows-Authenticate. (I user the administrator
to login to the server).
It seems some-virus has attacked this server because I found under the
administrators group, the user name of "guest" is there. I have disabled this
guest account now.
Please tell me how to run up the Enterprise Manager? Thanks a lot.
Are you able to ping the SQL Server machine? Where are you loading the
Enterprise Manager from? is it directly on the SQL Server? It looks like a
connectivity issue to me
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:6D183EDD-FAEA-49C8-A84C-EC0B1B09C9C8@.microsoft.com...
SQL Server does not exist or access denied!
Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data,even after
restart the computer. (does it means the sa password still correct?)
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer". Either with sa or Windows-Authenticate. (I user the administrator
to login to the server).
It seems some-virus has attacked this server because I found under the
administrators group, the user name of "guest" is there. I have disabled
this
guest account now.
Please tell me how to run up the Enterprise Manager? Thanks a lot.
|||Thanks, Narayana,
I'm trying to run the Enterprise Manager on another computer.
If run Enterprise Manager on the server, the error message is:"connection
failed,check SQL Server Registration Properties."
Error dialog is: A connection could not be established to server\instance.
Reason: Timeout expired.
=====
If run the query analyzer on the server, also can not (with sa or Windows
Authenticate)
"Narayana Vyas Kondreddi" wrote:

> Are you able to ping the SQL Server machine? Where are you loading the
> Enterprise Manager from? is it directly on the SQL Server? It looks like a
> connectivity issue to me
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
|||And this system has been running for some months. The Enterprise Manger and
query-analyzer run well before. Just for some weeks I didn't look it, then I
cannot login.
I'm sure the server has been infected by some virus. But how can I run
enterprise manager?
The website is still working well.
"goldenshine" wrote:
[vbcol=seagreen]
> Thanks, Narayana,
> I'm trying to run the Enterprise Manager on another computer.
> If run Enterprise Manager on the server, the error message is:"connection
> failed,check SQL Server Registration Properties."
> Error dialog is: A connection could not be established to server\instance.
> Reason: Timeout expired.
> =====
> If run the query analyzer on the server, also can not (with sa or Windows
> Authenticate)
> "Narayana Vyas Kondreddi" wrote:
|||Is the system too busy? Is the CPU maxed out? From control panel, make sure
the ODBC tracing is turned off.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:4A77150D-749F-4196-A283-6BD5E8151D23@.microsoft.com...
And this system has been running for some months. The Enterprise Manger and
query-analyzer run well before. Just for some weeks I didn't look it, then I
cannot login.
I'm sure the server has been infected by some virus. But how can I run
enterprise manager?
The website is still working well.
"goldenshine" wrote:
[vbcol=seagreen]
> Thanks, Narayana,
> I'm trying to run the Enterprise Manager on another computer.
> If run Enterprise Manager on the server, the error message is:"connection
> failed,check SQL Server Registration Properties."
> Error dialog is: A connection could not be established to server\instance.
> Reason: Timeout expired.
> =====
> If run the query analyzer on the server, also can not (with sa or Windows
> Authenticate)
> "Narayana Vyas Kondreddi" wrote:
a[vbcol=seagreen]
|||If the SS server has been running for several weeks without a reboot, then
from a machine that can use Enterprise manager check the instance to see if
there are any exchange waits. We have had issues where network issues have
caused 3 or more sessions to go into an exchange wait state that seems to
block normal user signons.
You might have to use Query Analyzer and run a statement like
select lastwaittype, waittime, loginame, spid, b.name, uid, physical_io,
last_batch,open_tran,a.status,loginame,hostname,pr ogram_name,cmd,net_address
from sysprocesses a left join sysdatabases b on b.dbid=a.dbid
where cmd not in ('LAZY WRITER','LOG WRITER','CHECKPOINT SLEEP','LOCK
MONITOR')
and waittime>0 order by lastwaittype,waittime
(wait type 200 may show up, it is an exchange wait.)
If you run this statement a couple of times and 3 or more sessions show up
every time, then you need to boot the server. At least that has been our
experience.
Joseph R.P. Maloney, CSP,CCP,CDP
"Narayana Vyas Kondreddi" wrote:

> Is the system too busy? Is the CPU maxed out? From control panel, make sure
> the ODBC tracing is turned off.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
> news:4A77150D-749F-4196-A283-6BD5E8151D23@.microsoft.com...
> And this system has been running for some months. The Enterprise Manger and
> query-analyzer run well before. Just for some weeks I didn't look it, then I
> cannot login.
> I'm sure the server has been infected by some virus. But how can I run
> enterprise manager?
> The website is still working well.
> "goldenshine" wrote:
> a
>
>
|||Thanks,
I'll restart the server some times, try to see how...
Currently Query Analyzer also cannot run.
"jrpm" wrote:
[vbcol=seagreen]
> If the SS server has been running for several weeks without a reboot, then
> from a machine that can use Enterprise manager check the instance to see if
> there are any exchange waits. We have had issues where network issues have
> caused 3 or more sessions to go into an exchange wait state that seems to
> block normal user signons.
> You might have to use Query Analyzer and run a statement like
>
> select lastwaittype, waittime, loginame, spid, b.name, uid, physical_io,
> last_batch,open_tran,a.status,loginame,hostname,pr ogram_name,cmd,net_address
> from sysprocesses a left join sysdatabases b on b.dbid=a.dbid
> where cmd not in ('LAZY WRITER','LOG WRITER','CHECKPOINT SLEEP','LOCK
> MONITOR')
> and waittime>0 order by lastwaittype,waittime
> (wait type 200 may show up, it is an exchange wait.)
> If you run this statement a couple of times and 3 or more sessions show up
> every time, then you need to boot the server. At least that has been our
> experience.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "Narayana Vyas Kondreddi" wrote:

Log-In error

SQL Server does not exist or access denied!
Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data,even after
restart the computer. (does it means the sa password still correct?)
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer". Either with sa or Windows-Authenticate. (I user the administrator
to login to the server).
It seems some-virus has attacked this server because I found under the
administrators group, the user name of "guest" is there. I have disabled thi
s
guest account now.
Please tell me how to run up the Enterprise Manager? Thanks a lot.Are you able to ping the SQL Server machine? Where are you loading the
Enterprise Manager from? is it directly on the SQL Server? It looks like a
connectivity issue to me
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:6D183EDD-FAEA-49C8-A84C-EC0B1B09C9C8@.microsoft.com...
SQL Server does not exist or access denied!
Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data,even after
restart the computer. (does it means the sa password still correct?)
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer". Either with sa or Windows-Authenticate. (I user the administrator
to login to the server).
It seems some-virus has attacked this server because I found under the
administrators group, the user name of "guest" is there. I have disabled
this
guest account now.
Please tell me how to run up the Enterprise Manager? Thanks a lot.|||Thanks, Narayana,
I'm trying to run the Enterprise Manager on another computer.
If run Enterprise Manager on the server, the error message is:"connection
failed,check SQL Server Registration Properties."
Error dialog is: A connection could not be established to server\instance.
Reason: Timeout expired.
=====
If run the query analyzer on the server, also can not (with sa or Windows
Authenticate)
"Narayana Vyas Kondreddi" wrote:

> Are you able to ping the SQL Server machine? Where are you loading the
> Enterprise Manager from? is it directly on the SQL Server? It looks like a
> connectivity issue to me
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>|||And this system has been running for some months. The Enterprise Manger and
query-analyzer run well before. Just for some weeks I didn't look it, then I
cannot login.
I'm sure the server has been infected by some virus. But how can I run
enterprise manager?
The website is still working well.
"goldenshine" wrote:
[vbcol=seagreen]
> Thanks, Narayana,
> I'm trying to run the Enterprise Manager on another computer.
> If run Enterprise Manager on the server, the error message is:"connection
> failed,check SQL Server Registration Properties."
> Error dialog is: A connection could not be established to server\instance.
> Reason: Timeout expired.
> =====
> If run the query analyzer on the server, also can not (with sa or Windows
> Authenticate)
> "Narayana Vyas Kondreddi" wrote:
>|||Is the system too busy? Is the CPU maxed out? From control panel, make sure
the ODBC tracing is turned off.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:4A77150D-749F-4196-A283-6BD5E8151D23@.microsoft.com...
And this system has been running for some months. The Enterprise Manger and
query-analyzer run well before. Just for some weeks I didn't look it, then I
cannot login.
I'm sure the server has been infected by some virus. But how can I run
enterprise manager?
The website is still working well.
"goldenshine" wrote:
[vbcol=seagreen]
> Thanks, Narayana,
> I'm trying to run the Enterprise Manager on another computer.
> If run Enterprise Manager on the server, the error message is:"connection
> failed,check SQL Server Registration Properties."
> Error dialog is: A connection could not be established to server\instance.
> Reason: Timeout expired.
> =====
> If run the query analyzer on the server, also can not (with sa or Windows
> Authenticate)
> "Narayana Vyas Kondreddi" wrote:
>
a[vbcol=seagreen]|||If the SS server has been running for several weeks without a reboot, then
from a machine that can use Enterprise manager check the instance to see if
there are any exchange waits. We have had issues where network issues have
caused 3 or more sessions to go into an exchange wait state that seems to
block normal user signons.
You might have to use Query Analyzer and run a statement like
select lastwaittype, waittime, loginame, spid, b.name, uid, physical_io,
last_batch,open_tran,a. status,loginame,hostname,program_name,cm
d,net_address
from sysprocesses a left join sysdatabases b on b.dbid=a.dbid
where cmd not in ('LAZY WRITER','LOG WRITER','CHECKPOINT SLEEP','LOCK
MONITOR')
and waittime>0 order by lastwaittype,waittime
(wait type 200 may show up, it is an exchange wait.)
If you run this statement a couple of times and 3 or more sessions show up
every time, then you need to boot the server. At least that has been our
experience.
Joseph R.P. Maloney, CSP,CCP,CDP
"Narayana Vyas Kondreddi" wrote:

> Is the system too busy? Is the CPU maxed out? From control panel, make sur
e
> the ODBC tracing is turned off.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
> news:4A77150D-749F-4196-A283-6BD5E8151D23@.microsoft.com...
> And this system has been running for some months. The Enterprise Manger an
d
> query-analyzer run well before. Just for some weeks I didn't look it, then
I
> cannot login.
> I'm sure the server has been infected by some virus. But how can I run
> enterprise manager?
> The website is still working well.
> "goldenshine" wrote:
>
> a
>
>|||Thanks,
I'll restart the server some times, try to see how...
Currently Query Analyzer also cannot run.
"jrpm" wrote:
[vbcol=seagreen]
> If the SS server has been running for several weeks without a reboot, then
> from a machine that can use Enterprise manager check the instance to see i
f
> there are any exchange waits. We have had issues where network issues ha
ve
> caused 3 or more sessions to go into an exchange wait state that seems to
> block normal user signons.
> You might have to use Query Analyzer and run a statement like
>
> select lastwaittype, waittime, loginame, spid, b.name, uid, physical_io,
> last_batch,open_tran,a. status,loginame,hostname,program_name,cm
d,net_addre
ss
> from sysprocesses a left join sysdatabases b on b.dbid=a.dbid
> where cmd not in ('LAZY WRITER','LOG WRITER','CHECKPOINT SLEEP','LOCK
> MONITOR')
> and waittime>0 order by lastwaittype,waittime
> (wait type 200 may show up, it is an exchange wait.)
> If you run this statement a couple of times and 3 or more sessions show up
> every time, then you need to boot the server. At least that has been our
> experience.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "Narayana Vyas Kondreddi" wrote:
>

Log-In error

SQL Server does not exist or access denied!
Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data,even after
restart the computer. (does it means the sa password still correct?)
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer". Either with sa or Windows-Authenticate. (I user the administrator
to login to the server).
It seems some-virus has attacked this server because I found under the
administrators group, the user name of "guest" is there. I have disabled this
guest account now.
Please tell me how to run up the Enterprise Manager? Thanks a lot.Are you able to ping the SQL Server machine? Where are you loading the
Enterprise Manager from? is it directly on the SQL Server? It looks like a
connectivity issue to me
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:6D183EDD-FAEA-49C8-A84C-EC0B1B09C9C8@.microsoft.com...
SQL Server does not exist or access denied!
Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data,even after
restart the computer. (does it means the sa password still correct?)
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer". Either with sa or Windows-Authenticate. (I user the administrator
to login to the server).
It seems some-virus has attacked this server because I found under the
administrators group, the user name of "guest" is there. I have disabled
this
guest account now.
Please tell me how to run up the Enterprise Manager? Thanks a lot.|||Thanks, Narayana,
I'm trying to run the Enterprise Manager on another computer.
If run Enterprise Manager on the server, the error message is:"connection
failed,check SQL Server Registration Properties."
Error dialog is: A connection could not be established to server\instance.
Reason: Timeout expired.
=====If run the query analyzer on the server, also can not (with sa or Windows
Authenticate)
"Narayana Vyas Kondreddi" wrote:
> Are you able to ping the SQL Server machine? Where are you loading the
> Enterprise Manager from? is it directly on the SQL Server? It looks like a
> connectivity issue to me
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>|||And this system has been running for some months. The Enterprise Manger and
query-analyzer run well before. Just for some weeks I didn't look it, then I
cannot login.
I'm sure the server has been infected by some virus. But how can I run
enterprise manager?
The website is still working well.
"goldenshine" wrote:
> Thanks, Narayana,
> I'm trying to run the Enterprise Manager on another computer.
> If run Enterprise Manager on the server, the error message is:"connection
> failed,check SQL Server Registration Properties."
> Error dialog is: A connection could not be established to server\instance.
> Reason: Timeout expired.
> =====> If run the query analyzer on the server, also can not (with sa or Windows
> Authenticate)
> "Narayana Vyas Kondreddi" wrote:
> > Are you able to ping the SQL Server machine? Where are you loading the
> > Enterprise Manager from? is it directly on the SQL Server? It looks like a
> > connectivity issue to me
> > --
> > HTH,
> > Vyas, MVP (SQL Server)
> > SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
> >
> >|||Is the system too busy? Is the CPU maxed out? From control panel, make sure
the ODBC tracing is turned off.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:4A77150D-749F-4196-A283-6BD5E8151D23@.microsoft.com...
And this system has been running for some months. The Enterprise Manger and
query-analyzer run well before. Just for some weeks I didn't look it, then I
cannot login.
I'm sure the server has been infected by some virus. But how can I run
enterprise manager?
The website is still working well.
"goldenshine" wrote:
> Thanks, Narayana,
> I'm trying to run the Enterprise Manager on another computer.
> If run Enterprise Manager on the server, the error message is:"connection
> failed,check SQL Server Registration Properties."
> Error dialog is: A connection could not be established to server\instance.
> Reason: Timeout expired.
> =====> If run the query analyzer on the server, also can not (with sa or Windows
> Authenticate)
> "Narayana Vyas Kondreddi" wrote:
> > Are you able to ping the SQL Server machine? Where are you loading the
> > Enterprise Manager from? is it directly on the SQL Server? It looks like
a
> > connectivity issue to me
> > --
> > HTH,
> > Vyas, MVP (SQL Server)
> > SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
> >
> >|||If the SS server has been running for several weeks without a reboot, then
from a machine that can use Enterprise manager check the instance to see if
there are any exchange waits. We have had issues where network issues have
caused 3 or more sessions to go into an exchange wait state that seems to
block normal user signons.
You might have to use Query Analyzer and run a statement like
select lastwaittype, waittime, loginame, spid, b.name, uid, physical_io,
last_batch,open_tran,a.status,loginame,hostname,program_name,cmd,net_address
from sysprocesses a left join sysdatabases b on b.dbid=a.dbid
where cmd not in ('LAZY WRITER','LOG WRITER','CHECKPOINT SLEEP','LOCK
MONITOR')
and waittime>0 order by lastwaittype,waittime
(wait type 200 may show up, it is an exchange wait.)
If you run this statement a couple of times and 3 or more sessions show up
every time, then you need to boot the server. At least that has been our
experience.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Narayana Vyas Kondreddi" wrote:
> Is the system too busy? Is the CPU maxed out? From control panel, make sure
> the ODBC tracing is turned off.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
> news:4A77150D-749F-4196-A283-6BD5E8151D23@.microsoft.com...
> And this system has been running for some months. The Enterprise Manger and
> query-analyzer run well before. Just for some weeks I didn't look it, then I
> cannot login.
> I'm sure the server has been infected by some virus. But how can I run
> enterprise manager?
> The website is still working well.
> "goldenshine" wrote:
> > Thanks, Narayana,
> > I'm trying to run the Enterprise Manager on another computer.
> > If run Enterprise Manager on the server, the error message is:"connection
> > failed,check SQL Server Registration Properties."
> > Error dialog is: A connection could not be established to server\instance.
> > Reason: Timeout expired.
> > =====> > If run the query analyzer on the server, also can not (with sa or Windows
> > Authenticate)
> >
> > "Narayana Vyas Kondreddi" wrote:
> >
> > > Are you able to ping the SQL Server machine? Where are you loading the
> > > Enterprise Manager from? is it directly on the SQL Server? It looks like
> a
> > > connectivity issue to me
> > > --
> > > HTH,
> > > Vyas, MVP (SQL Server)
> > > SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
> > >
> > >
>
>|||Thanks,
I'll restart the server some times, try to see how...
Currently Query Analyzer also cannot run.
"jrpm" wrote:
> If the SS server has been running for several weeks without a reboot, then
> from a machine that can use Enterprise manager check the instance to see if
> there are any exchange waits. We have had issues where network issues have
> caused 3 or more sessions to go into an exchange wait state that seems to
> block normal user signons.
> You might have to use Query Analyzer and run a statement like
>
> select lastwaittype, waittime, loginame, spid, b.name, uid, physical_io,
> last_batch,open_tran,a.status,loginame,hostname,program_name,cmd,net_address
> from sysprocesses a left join sysdatabases b on b.dbid=a.dbid
> where cmd not in ('LAZY WRITER','LOG WRITER','CHECKPOINT SLEEP','LOCK
> MONITOR')
> and waittime>0 order by lastwaittype,waittime
> (wait type 200 may show up, it is an exchange wait.)
> If you run this statement a couple of times and 3 or more sessions show up
> every time, then you need to boot the server. At least that has been our
> experience.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "Narayana Vyas Kondreddi" wrote:
> > Is the system too busy? Is the CPU maxed out? From control panel, make sure
> > the ODBC tracing is turned off.
> > --
> > HTH,
> > Vyas, MVP (SQL Server)
> > SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
> >
> >
> > "goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
> > news:4A77150D-749F-4196-A283-6BD5E8151D23@.microsoft.com...
> > And this system has been running for some months. The Enterprise Manger and
> > query-analyzer run well before. Just for some weeks I didn't look it, then I
> > cannot login.
> > I'm sure the server has been infected by some virus. But how can I run
> > enterprise manager?
> >
> > The website is still working well.
> >
> > "goldenshine" wrote:
> >
> > > Thanks, Narayana,
> > > I'm trying to run the Enterprise Manager on another computer.
> > > If run Enterprise Manager on the server, the error message is:"connection
> > > failed,check SQL Server Registration Properties."
> > > Error dialog is: A connection could not be established to server\instance.
> > > Reason: Timeout expired.
> > > =====> > > If run the query analyzer on the server, also can not (with sa or Windows
> > > Authenticate)
> > >
> > > "Narayana Vyas Kondreddi" wrote:
> > >
> > > > Are you able to ping the SQL Server machine? Where are you loading the
> > > > Enterprise Manager from? is it directly on the SQL Server? It looks like
> > a
> > > > connectivity issue to me
> > > > --
> > > > HTH,
> > > > Vyas, MVP (SQL Server)
> > > > SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
> > > >
> > > >
> >
> >
> >

Friday, March 9, 2012

Login

Hi,
I am under the impression that the master database contains all log-in
info for each database, is that correct?
How about the server log-in? If i need to do the server migration, i need
to transfer all the server log-in manually (or using DTS Transfer log-in task)
is that true?
Thanks a lot
Ed
See if this helps:
http://support.microsoft.com/default...b;en-us;246133
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:0FA72DC1-AF86-422E-96CA-FCB183B4FE66@.microsoft.com...
Hi,
I am under the impression that the master database contains all log-in
info for each database, is that correct?
How about the server log-in? If i need to do the server migration, i need
to transfer all the server log-in manually (or using DTS Transfer log-in
task)
is that true?
Thanks a lot
Ed
|||No that is not correct.
Server logins are kept in master.dbo.sysxlogins table, or better yet,
syslogins view.
Each database keeps their own user accounts in sysusers table.
When you move to a new server, you may encounter orphaned users when
restoring databases because the new server SID does not match the source
SID. You can use sp_change_users_login to resync the SID, or use
sp_help_revlogin to script out all logins with their original SIDs and run
it to create logins on the new server.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:0FA72DC1-AF86-422E-96CA-FCB183B4FE66@.microsoft.com...
> Hi,
> I am under the impression that the master database contains all log-in
> info for each database, is that correct?
> How about the server log-in? If i need to do the server migration, i
need
> to transfer all the server log-in manually (or using DTS Transfer log-in
task)
> is that true?
> Thanks a lot
> Ed
|||Richard,
So if i do a server migration, I need to take care of the Server Log-in
first or User databases Log-in first or doesn't matter...
Thanks again
Ed
"Richard Ding" wrote:

> No that is not correct.
> Server logins are kept in master.dbo.sysxlogins table, or better yet,
> syslogins view.
> Each database keeps their own user accounts in sysusers table.
> When you move to a new server, you may encounter orphaned users when
> restoring databases because the new server SID does not match the source
> SID. You can use sp_change_users_login to resync the SID, or use
> sp_help_revlogin to script out all logins with their original SIDs and run
> it to create logins on the new server.
>
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:0FA72DC1-AF86-422E-96CA-FCB183B4FE66@.microsoft.com...
> need
> task)
>
>
|||The way I do when migrate server is to install the SQL server first. then
use sp_help_revlogin to create all logins on the new server. Next start
restoring user databases as well as msdb.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:C385D215-78F3-41BF-92BB-6F5431A1BC44@.microsoft.com...[vbcol=seagreen]
> Richard,
> So if i do a server migration, I need to take care of the Server Log-in
> first or User databases Log-in first or doesn't matter...
> Thanks again
> Ed
> "Richard Ding" wrote:
run[vbcol=seagreen]
log-in[vbcol=seagreen]
i[vbcol=seagreen]
log-in[vbcol=seagreen]
|||Richard,
Do you also have any idea about how to restore the Master Database?
What I am planning to do is
1. Backup (Old Server) all the databases (User and System) to a share folder
2. Create each individual user database in New Server
3. Restore each user database and retrive the backup files from the share
folder
4. Restore MSDB, MODEL database
5. Use DTS to transfer all the server log-in to New Server
is there anything wrong on doing this? How about dealing with the Master
Database, it needs to be transfered, too......
Thank you very much
Ed
"Richard Ding" wrote:

> The way I do when migrate server is to install the SQL server first. then
> use sp_help_revlogin to create all logins on the new server. Next start
> restoring user databases as well as msdb.
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:C385D215-78F3-41BF-92BB-6F5431A1BC44@.microsoft.com...
> run
> log-in
> i
> log-in
>
>
|||If you plan to restore master, you need to put the server in single user
mode and run restore master from tape or disk. Refer to BOL on "how to
restore master db".
You don't need to do 2. Try restore master first then user dbs.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:CB2F7FD9-22F4-4721-B60E-8988C2589062@.microsoft.com...
> Richard,
> Do you also have any idea about how to restore the Master Database?
> What I am planning to do is
> 1. Backup (Old Server) all the databases (User and System) to a share
folder[vbcol=seagreen]
> 2. Create each individual user database in New Server
> 3. Restore each user database and retrive the backup files from the share
> folder
> 4. Restore MSDB, MODEL database
> 5. Use DTS to transfer all the server log-in to New Server
> is there anything wrong on doing this? How about dealing with the Master
> Database, it needs to be transfered, too......
> Thank you very much
> Ed
>
>
> "Richard Ding" wrote:
then[vbcol=seagreen]
Log-in[vbcol=seagreen]
yet,[vbcol=seagreen]
source[vbcol=seagreen]
and[vbcol=seagreen]
migration,[vbcol=seagreen]

Login

Hi,
I am under the impression that the master database contains all log-in
info for each database, is that correct?
How about the server log-in? If i need to do the server migration, i need
to transfer all the server log-in manually (or using DTS Transfer log-in tas
k)
is that true?
Thanks a lot
EdSee if this helps:
http://support.microsoft.com/defaul...kb;en-us;246133
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:0FA72DC1-AF86-422E-96CA-FCB183B4FE66@.microsoft.com...
Hi,
I am under the impression that the master database contains all log-in
info for each database, is that correct?
How about the server log-in? If i need to do the server migration, i need
to transfer all the server log-in manually (or using DTS Transfer log-in
task)
is that true?
Thanks a lot
Ed|||No that is not correct.
Server logins are kept in master.dbo.sysxlogins table, or better yet,
syslogins view.
Each database keeps their own user accounts in sysusers table.
When you move to a new server, you may encounter orphaned users when
restoring databases because the new server SID does not match the source
SID. You can use sp_change_users_login to resync the SID, or use
sp_help_revlogin to script out all logins with their original SIDs and run
it to create logins on the new server.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:0FA72DC1-AF86-422E-96CA-FCB183B4FE66@.microsoft.com...
> Hi,
> I am under the impression that the master database contains all log-in
> info for each database, is that correct?
> How about the server log-in? If i need to do the server migration, i
need
> to transfer all the server log-in manually (or using DTS Transfer log-in
task)
> is that true?
> Thanks a lot
> Ed|||Richard,
So if i do a server migration, I need to take care of the Server Log-in
first or User databases Log-in first or doesn't matter...
Thanks again
Ed
"Richard Ding" wrote:

> No that is not correct.
> Server logins are kept in master.dbo.sysxlogins table, or better yet,
> syslogins view.
> Each database keeps their own user accounts in sysusers table.
> When you move to a new server, you may encounter orphaned users when
> restoring databases because the new server SID does not match the source
> SID. You can use sp_change_users_login to resync the SID, or use
> sp_help_revlogin to script out all logins with their original SIDs and run
> it to create logins on the new server.
>
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:0FA72DC1-AF86-422E-96CA-FCB183B4FE66@.microsoft.com...
> need
> task)
>
>|||The way I do when migrate server is to install the SQL server first. then
use sp_help_revlogin to create all logins on the new server. Next start
restoring user databases as well as msdb.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:C385D215-78F3-41BF-92BB-6F5431A1BC44@.microsoft.com...[vbcol=seagreen]
> Richard,
> So if i do a server migration, I need to take care of the Server Log-in
> first or User databases Log-in first or doesn't matter...
> Thanks again
> Ed
> "Richard Ding" wrote:
>
run[vbcol=seagreen]
log-in[vbcol=seagreen]
i[vbcol=seagreen]
log-in[vbcol=seagreen]|||Richard,
Do you also have any idea about how to restore the Master Database?
What I am planning to do is
1. Backup (Old Server) all the databases (User and System) to a share folder
2. Create each individual user database in New Server
3. Restore each user database and retrive the backup files from the share
folder
4. Restore MSDB, MODEL database
5. Use DTS to transfer all the server log-in to New Server
is there anything wrong on doing this? How about dealing with the Master
Database, it needs to be transfered, too......
Thank you very much
Ed
"Richard Ding" wrote:

> The way I do when migrate server is to install the SQL server first. then
> use sp_help_revlogin to create all logins on the new server. Next start
> restoring user databases as well as msdb.
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:C385D215-78F3-41BF-92BB-6F5431A1BC44@.microsoft.com...
> run
> log-in
> i
> log-in
>
>|||If you plan to restore master, you need to put the server in single user
mode and run restore master from tape or disk. Refer to BOL on "how to
restore master db".
You don't need to do 2. Try restore master first then user dbs.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:CB2F7FD9-22F4-4721-B60E-8988C2589062@.microsoft.com...
> Richard,
> Do you also have any idea about how to restore the Master Database?
> What I am planning to do is
> 1. Backup (Old Server) all the databases (User and System) to a share
folder[vbcol=seagreen]
> 2. Create each individual user database in New Server
> 3. Restore each user database and retrive the backup files from the share
> folder
> 4. Restore MSDB, MODEL database
> 5. Use DTS to transfer all the server log-in to New Server
> is there anything wrong on doing this? How about dealing with the Master
> Database, it needs to be transfered, too......
> Thank you very much
> Ed
>
>
> "Richard Ding" wrote:
>
then[vbcol=seagreen]
Log-in[vbcol=seagreen]
yet,[vbcol=seagreen]
source[vbcol=seagreen]
and[vbcol=seagreen]
migration,[vbcol=seagreen]