Hello group,
We have a query that calculates certain dates, etc. It runs very slow on
this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
Windows 2003 server and SQL 2000. If you copy the database over to another
server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
and run the same query it runs in 2-3 minutes. This is a huge gap of time
and I don't see a whole lot of performance changes using perfmon on the
troubled server.
Any ideas what I can use to troubleshoot this? Do you think this may be
hardware related or database or ?
TIA,
Jason
There can be many reasons. Did you verify using sp_who that this query is
not getting blocked? Did you monitor the physical disk counters to see if
there are any issues with disk subsystem performance?
What about the execution plans? Did you compare the execution plan of the
queries between your server and workstation? This will help in determining
any missing indexes or out of date stats.
Worth checking the fragmentation on your bigger tables and also updating the
statistics.
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Jason King" <jasonk@.bham.wednet.edu> wrote in message
news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hello group,
> We have a query that calculates certain dates, etc. It runs very slow on
> this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
> Windows 2003 server and SQL 2000. If you copy the database over to another
> server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
> and run the same query it runs in 2-3 minutes. This is a huge gap of time
> and I don't see a whole lot of performance changes using perfmon on the
> troubled server.
> Any ideas what I can use to troubleshoot this? Do you think this may be
> hardware related or database or ?
> TIA,
> Jason
>
|||Thanks. We found the problem. It was due to passing NULL parameters within
the SP for retrieving certain dates. If we call the dates first then execute
the procedure without any NULL parameters, it runs very fast.
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:uIDsfRnOFHA.3280@.TK2MSFTNGP10.phx.gbl...
> There can be many reasons. Did you verify using sp_who that this query is
> not getting blocked? Did you monitor the physical disk counters to see if
> there are any issues with disk subsystem performance?
> What about the execution plans? Did you compare the execution plan of the
> queries between your server and workstation? This will help in determining
> any missing indexes or out of date stats.
> Worth checking the fragmentation on your bigger tables and also updating
the[vbcol=seagreen]
> statistics.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Jason King" <jasonk@.bham.wednet.edu> wrote in message
> news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
running[vbcol=seagreen]
another[vbcol=seagreen]
ram)[vbcol=seagreen]
time
>
sql
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Wednesday, March 28, 2012
Long running query
Hello group,
We have a query that calculates certain dates, etc. It runs very slow on
this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
Windows 2003 server and SQL 2000. If you copy the database over to another
server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
and run the same query it runs in 2-3 minutes. This is a huge gap of time
and I don't see a whole lot of performance changes using perfmon on the
troubled server.
Any ideas what I can use to troubleshoot this? Do you think this may be
hardware related or database or '
TIA,
JasonThere can be many reasons. Did you verify using sp_who that this query is
not getting blocked? Did you monitor the physical disk counters to see if
there are any issues with disk subsystem performance?
What about the execution plans? Did you compare the execution plan of the
queries between your server and workstation? This will help in determining
any missing indexes or out of date stats.
Worth checking the fragmentation on your bigger tables and also updating the
statistics.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Jason King" <jasonk@.bham.wednet.edu> wrote in message
news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hello group,
> We have a query that calculates certain dates, etc. It runs very slow on
> this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
> Windows 2003 server and SQL 2000. If you copy the database over to another
> server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
> and run the same query it runs in 2-3 minutes. This is a huge gap of time
> and I don't see a whole lot of performance changes using perfmon on the
> troubled server.
> Any ideas what I can use to troubleshoot this? Do you think this may be
> hardware related or database or '
> TIA,
> Jason
>|||Thanks. We found the problem. It was due to passing NULL parameters within
the SP for retrieving certain dates. If we call the dates first then execute
the procedure without any NULL parameters, it runs very fast.
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:uIDsfRnOFHA.3280@.TK2MSFTNGP10.phx.gbl...
> There can be many reasons. Did you verify using sp_who that this query is
> not getting blocked? Did you monitor the physical disk counters to see if
> there are any issues with disk subsystem performance?
> What about the execution plans? Did you compare the execution plan of the
> queries between your server and workstation? This will help in determining
> any missing indexes or out of date stats.
> Worth checking the fragmentation on your bigger tables and also updating
the
> statistics.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Jason King" <jasonk@.bham.wednet.edu> wrote in message
> news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
running[vbcol=seagreen]
another[vbcol=seagreen]
ram)[vbcol=seagreen]
time[vbcol=seagreen]
>
We have a query that calculates certain dates, etc. It runs very slow on
this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
Windows 2003 server and SQL 2000. If you copy the database over to another
server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
and run the same query it runs in 2-3 minutes. This is a huge gap of time
and I don't see a whole lot of performance changes using perfmon on the
troubled server.
Any ideas what I can use to troubleshoot this? Do you think this may be
hardware related or database or '
TIA,
JasonThere can be many reasons. Did you verify using sp_who that this query is
not getting blocked? Did you monitor the physical disk counters to see if
there are any issues with disk subsystem performance?
What about the execution plans? Did you compare the execution plan of the
queries between your server and workstation? This will help in determining
any missing indexes or out of date stats.
Worth checking the fragmentation on your bigger tables and also updating the
statistics.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Jason King" <jasonk@.bham.wednet.edu> wrote in message
news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hello group,
> We have a query that calculates certain dates, etc. It runs very slow on
> this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
> Windows 2003 server and SQL 2000. If you copy the database over to another
> server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
> and run the same query it runs in 2-3 minutes. This is a huge gap of time
> and I don't see a whole lot of performance changes using perfmon on the
> troubled server.
> Any ideas what I can use to troubleshoot this? Do you think this may be
> hardware related or database or '
> TIA,
> Jason
>|||Thanks. We found the problem. It was due to passing NULL parameters within
the SP for retrieving certain dates. If we call the dates first then execute
the procedure without any NULL parameters, it runs very fast.
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:uIDsfRnOFHA.3280@.TK2MSFTNGP10.phx.gbl...
> There can be many reasons. Did you verify using sp_who that this query is
> not getting blocked? Did you monitor the physical disk counters to see if
> there are any issues with disk subsystem performance?
> What about the execution plans? Did you compare the execution plan of the
> queries between your server and workstation? This will help in determining
> any missing indexes or out of date stats.
> Worth checking the fragmentation on your bigger tables and also updating
the
> statistics.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Jason King" <jasonk@.bham.wednet.edu> wrote in message
> news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
running[vbcol=seagreen]
another[vbcol=seagreen]
ram)[vbcol=seagreen]
time[vbcol=seagreen]
>
Long running query
Hello group,
We have a query that calculates certain dates, etc. It runs very slow on
this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
Windows 2003 server and SQL 2000. If you copy the database over to another
server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
and run the same query it runs in 2-3 minutes. This is a huge gap of time
and I don't see a whole lot of performance changes using perfmon on the
troubled server.
Any ideas what I can use to troubleshoot this? Do you think this may be
hardware related or database or '
TIA,
JasonThere can be many reasons. Did you verify using sp_who that this query is
not getting blocked? Did you monitor the physical disk counters to see if
there are any issues with disk subsystem performance?
What about the execution plans? Did you compare the execution plan of the
queries between your server and workstation? This will help in determining
any missing indexes or out of date stats.
Worth checking the fragmentation on your bigger tables and also updating the
statistics.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Jason King" <jasonk@.bham.wednet.edu> wrote in message
news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hello group,
> We have a query that calculates certain dates, etc. It runs very slow on
> this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
> Windows 2003 server and SQL 2000. If you copy the database over to another
> server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
> and run the same query it runs in 2-3 minutes. This is a huge gap of time
> and I don't see a whole lot of performance changes using perfmon on the
> troubled server.
> Any ideas what I can use to troubleshoot this? Do you think this may be
> hardware related or database or '
> TIA,
> Jason
>|||Thanks. We found the problem. It was due to passing NULL parameters within
the SP for retrieving certain dates. If we call the dates first then execute
the procedure without any NULL parameters, it runs very fast.
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:uIDsfRnOFHA.3280@.TK2MSFTNGP10.phx.gbl...
> There can be many reasons. Did you verify using sp_who that this query is
> not getting blocked? Did you monitor the physical disk counters to see if
> there are any issues with disk subsystem performance?
> What about the execution plans? Did you compare the execution plan of the
> queries between your server and workstation? This will help in determining
> any missing indexes or out of date stats.
> Worth checking the fragmentation on your bigger tables and also updating
the
> statistics.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Jason King" <jasonk@.bham.wednet.edu> wrote in message
> news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
> > Hello group,
> >
> > We have a query that calculates certain dates, etc. It runs very slow on
> > this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM
running
> > Windows 2003 server and SQL 2000. If you copy the database over to
another
> > server or XP workstation (even running a single 2.6 GHZ CPU with 1gb
ram)
> > and run the same query it runs in 2-3 minutes. This is a huge gap of
time
> > and I don't see a whole lot of performance changes using perfmon on the
> > troubled server.
> >
> > Any ideas what I can use to troubleshoot this? Do you think this may be
> > hardware related or database or '
> >
> > TIA,
> >
> > Jason
> >
> >
>
We have a query that calculates certain dates, etc. It runs very slow on
this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
Windows 2003 server and SQL 2000. If you copy the database over to another
server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
and run the same query it runs in 2-3 minutes. This is a huge gap of time
and I don't see a whole lot of performance changes using perfmon on the
troubled server.
Any ideas what I can use to troubleshoot this? Do you think this may be
hardware related or database or '
TIA,
JasonThere can be many reasons. Did you verify using sp_who that this query is
not getting blocked? Did you monitor the physical disk counters to see if
there are any issues with disk subsystem performance?
What about the execution plans? Did you compare the execution plan of the
queries between your server and workstation? This will help in determining
any missing indexes or out of date stats.
Worth checking the fragmentation on your bigger tables and also updating the
statistics.
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Jason King" <jasonk@.bham.wednet.edu> wrote in message
news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hello group,
> We have a query that calculates certain dates, etc. It runs very slow on
> this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM running
> Windows 2003 server and SQL 2000. If you copy the database over to another
> server or XP workstation (even running a single 2.6 GHZ CPU with 1gb ram)
> and run the same query it runs in 2-3 minutes. This is a huge gap of time
> and I don't see a whole lot of performance changes using perfmon on the
> troubled server.
> Any ideas what I can use to troubleshoot this? Do you think this may be
> hardware related or database or '
> TIA,
> Jason
>|||Thanks. We found the problem. It was due to passing NULL parameters within
the SP for retrieving certain dates. If we call the dates first then execute
the procedure without any NULL parameters, it runs very fast.
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:uIDsfRnOFHA.3280@.TK2MSFTNGP10.phx.gbl...
> There can be many reasons. Did you verify using sp_who that this query is
> not getting blocked? Did you monitor the physical disk counters to see if
> there are any issues with disk subsystem performance?
> What about the execution plans? Did you compare the execution plan of the
> queries between your server and workstation? This will help in determining
> any missing indexes or out of date stats.
> Worth checking the fragmentation on your bigger tables and also updating
the
> statistics.
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Jason King" <jasonk@.bham.wednet.edu> wrote in message
> news:%23ETRjMgOFHA.3356@.TK2MSFTNGP12.phx.gbl...
> > Hello group,
> >
> > We have a query that calculates certain dates, etc. It runs very slow on
> > this server (3 hours!) which is a Gateway quad 600mhz with 2GB RAM
running
> > Windows 2003 server and SQL 2000. If you copy the database over to
another
> > server or XP workstation (even running a single 2.6 GHZ CPU with 1gb
ram)
> > and run the same query it runs in 2-3 minutes. This is a huge gap of
time
> > and I don't see a whole lot of performance changes using perfmon on the
> > troubled server.
> >
> > Any ideas what I can use to troubleshoot this? Do you think this may be
> > hardware related or database or '
> >
> > TIA,
> >
> > Jason
> >
> >
>
Monday, March 19, 2012
Logon failure
To get my reports to work from the 2005 Report Manager I had to put the
Execution Account into the Local Administrators Group, otherwise I got a
Logon Failoure message when attempting to view the report. Is this how it's
sipposed to be?Don't use anonymous access with windows authentication......
Kinda defeats the purpose.
"Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
news:8453498E-99F8-43AA-8ADD-9005C6F2FF35@.microsoft.com...
> To get my reports to work from the 2005 Report Manager I had to put the
> Execution Account into the Local Administrators Group, otherwise I got a
> Logon Failoure message when attempting to view the report. Is this how
> it's
> sipposed to be?|||What do you mean about Anonymous access? In the Report Configuration page I
had a limited donain account set for the services and the execution account.
When a report was selected to be viewed a logon failure error resulted saying
that "The user has not been granted the requested logon type at this machine
"
I was unable to figure out how to change the requested logon type, so I
added the account to the Local Administrators group and I no longer got the
Logon failure error. Now I thought that Microsoft was attempting to secure
the way that things worked so that an account as in this case would not need
to have such elevated permissions. I am looking for information that can
explain what is required for an account to be able to execute reports when
requested and validation that they have to be in the Administrative group.
The anonymous caused me confusion because I don't see where it comes into
play.
Thanks
"Chris Taylor" wrote:
> Don't use anonymous access with windows authentication......
> Kinda defeats the purpose.
> "Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
> news:8453498E-99F8-43AA-8ADD-9005C6F2FF35@.microsoft.com...
> > To get my reports to work from the 2005 Report Manager I had to put the
> > Execution Account into the Local Administrators Group, otherwise I got a
> > Logon Failoure message when attempting to view the report. Is this how
> > it's
> > sipposed to be?
>
>
Execution Account into the Local Administrators Group, otherwise I got a
Logon Failoure message when attempting to view the report. Is this how it's
sipposed to be?Don't use anonymous access with windows authentication......
Kinda defeats the purpose.
"Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
news:8453498E-99F8-43AA-8ADD-9005C6F2FF35@.microsoft.com...
> To get my reports to work from the 2005 Report Manager I had to put the
> Execution Account into the Local Administrators Group, otherwise I got a
> Logon Failoure message when attempting to view the report. Is this how
> it's
> sipposed to be?|||What do you mean about Anonymous access? In the Report Configuration page I
had a limited donain account set for the services and the execution account.
When a report was selected to be viewed a logon failure error resulted saying
that "The user has not been granted the requested logon type at this machine
"
I was unable to figure out how to change the requested logon type, so I
added the account to the Local Administrators group and I no longer got the
Logon failure error. Now I thought that Microsoft was attempting to secure
the way that things worked so that an account as in this case would not need
to have such elevated permissions. I am looking for information that can
explain what is required for an account to be able to execute reports when
requested and validation that they have to be in the Administrative group.
The anonymous caused me confusion because I don't see where it comes into
play.
Thanks
"Chris Taylor" wrote:
> Don't use anonymous access with windows authentication......
> Kinda defeats the purpose.
> "Jim Abel" <JimAbel@.discussions.microsoft.com> wrote in message
> news:8453498E-99F8-43AA-8ADD-9005C6F2FF35@.microsoft.com...
> > To get my reports to work from the 2005 Report Manager I had to put the
> > Execution Account into the Local Administrators Group, otherwise I got a
> > Logon Failoure message when attempting to view the report. Is this how
> > it's
> > sipposed to be?
>
>
Monday, March 12, 2012
Logins under Windows Group
Hi All,
I want to get all the Logins under Particular Windows Group by using Query
or System Stored Procedure.
For Eg: All Logins under BUILTIN\Administrators
Could anyone pls help me out?
Thanks in Advance...
Regards,
Herbert R.exec sp_helplogins
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:AC53F0BE-9938-4D4F-807B-833F00F5688E@.microsoft.com...
> Hi All,
> I want to get all the Logins under Particular Windows Group by using Query
> or System Stored Procedure.
> For Eg: All Logins under BUILTIN\Administrators
> Could anyone pls help me out?
> Thanks in Advance...
> Regards,
> Herbert R.
I want to get all the Logins under Particular Windows Group by using Query
or System Stored Procedure.
For Eg: All Logins under BUILTIN\Administrators
Could anyone pls help me out?
Thanks in Advance...
Regards,
Herbert R.exec sp_helplogins
"Herbert" <Herbert@.discussions.microsoft.com> wrote in message
news:AC53F0BE-9938-4D4F-807B-833F00F5688E@.microsoft.com...
> Hi All,
> I want to get all the Logins under Particular Windows Group by using Query
> or System Stored Procedure.
> For Eg: All Logins under BUILTIN\Administrators
> Could anyone pls help me out?
> Thanks in Advance...
> Regards,
> Herbert R.
Wednesday, March 7, 2012
Login to SQL Server
I have registered SQL server instance (SQLServer1) in SQL Server group,
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Seems like SQL Server only accepts Windows logins.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=mySQLServe r"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
>
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Seems like SQL Server only accepts Windows logins.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=mySQLServe r"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
>
Login to SQL Server
I have registered SQL server instance (SQLServer1) in SQL Server group,
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***Seems like SQL Server only accepts Windows logins.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx
.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=
mySQLServer"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
>
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***Seems like SQL Server only accepts Windows logins.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx
.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=
mySQLServer"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
>
Login to SQL Server
I have registered SQL server instance (SQLServer1) in SQL Server group,
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.developersdex.com ***Seems like SQL Server only accepts Windows logins.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=mySQLServer"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
--
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***
>
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.developersdex.com ***Seems like SQL Server only accepts Windows logins.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=mySQLServer"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
--
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***
>
Login succeeded followed by Logon Failed
We are experiencing some strange behaviour on SQL Server 2000. Certain
members of a domain group are unable to login. The error log says something
like
2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
Connection: Trusted.
2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
This is only affecting certain members of the group. (The SQL Server Error
msg says the user can not access their default database).Any suggestions as
to why this might be happening.stu,
If you are granting access to the server through domain groups rather that
to individual user accounts, then Accounts\Joe may be in several groups.
If he is in a group that has been assigned a default database to which he
does not have rights, then he _may_ fail to attach to his default database.
(Why won't everyone fail? Because they are not all members of the same
group and (as far as I have been able to discover) which group will provide
the default database for the user login is not deterministic.)
Actions:
1) Check to see if any Group Logins have a default database assignment to a
database in which they have no rights. If so, correct this.
2) Explicitly set the default database for the logins that are failing.
Even though all rights will still be granted through their group
memberships, the login account default database will have priority over any
group settings.
sp_defaultdb 'Accounts\Joe', 'GoodDefaultDB'
You do not have to create an Accounts\Joe login, but the sp_defaultdb will
create one for you in this case.
RLF
"stu" <stu@.discussions.microsoft.com> wrote in message
news:F8CDE8B3-B206-473A-94C5-F6A408B61064@.microsoft.com...
> We are experiencing some strange behaviour on SQL Server 2000. Certain
> members of a domain group are unable to login. The error log says
> something
> like
> 2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
> Connection: Trusted.
> 2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
> This is only affecting certain members of the group. (The SQL Server Error
> msg says the user can not access their default database).Any suggestions
> as
> to why this might be happening.
members of a domain group are unable to login. The error log says something
like
2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
Connection: Trusted.
2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
This is only affecting certain members of the group. (The SQL Server Error
msg says the user can not access their default database).Any suggestions as
to why this might be happening.stu,
If you are granting access to the server through domain groups rather that
to individual user accounts, then Accounts\Joe may be in several groups.
If he is in a group that has been assigned a default database to which he
does not have rights, then he _may_ fail to attach to his default database.
(Why won't everyone fail? Because they are not all members of the same
group and (as far as I have been able to discover) which group will provide
the default database for the user login is not deterministic.)
Actions:
1) Check to see if any Group Logins have a default database assignment to a
database in which they have no rights. If so, correct this.
2) Explicitly set the default database for the logins that are failing.
Even though all rights will still be granted through their group
memberships, the login account default database will have priority over any
group settings.
sp_defaultdb 'Accounts\Joe', 'GoodDefaultDB'
You do not have to create an Accounts\Joe login, but the sp_defaultdb will
create one for you in this case.
RLF
"stu" <stu@.discussions.microsoft.com> wrote in message
news:F8CDE8B3-B206-473A-94C5-F6A408B61064@.microsoft.com...
> We are experiencing some strange behaviour on SQL Server 2000. Certain
> members of a domain group are unable to login. The error log says
> something
> like
> 2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
> Connection: Trusted.
> 2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
> This is only affecting certain members of the group. (The SQL Server Error
> msg says the user can not access their default database).Any suggestions
> as
> to why this might be happening.
Friday, February 24, 2012
Login problem by not being in sysadmin group
Hi All
I experience a very strange login problem:
I create standard security login, let say test1/test1 with a default db test and assign it sysadmin group.
All is working well.
The moment remove sysadmin group from this login, i start getting errors:
Login failed for user 'test1'
... when I login from remote server. If I login from the same host - it continues with no problem.
When I go to sql server configuration manager, I see next:
sql native client configuration(32bit):
shared memeory enabled
tcp/ip enabled
named pipes enabled
VIA disabled
The same settings from sql server 2005 network configuration / protocols for mssqlserver
sql native client configuration / client protocols
sql 2005 surface area configuration / remote connections is configured:
local and remote connections (checked), using both tcp/ip and named pipes.
Does anybody have a clue?
What is the default database for your login?
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
|||Hi Wesley
Default db is named 'test'. I made sure login has default db and can browse it.
|||Try changing the default database to master. If you can then connect with that login, there is a problem with the users access to what you were using for the default database.
-Sue
Login problem by not being in sysadmin group
Hi All
I experience a very strange login problem:
I create standard security login, let say test1/test1 with a default db test and assign it sysadmin group.
All is working well.
The moment remove sysadmin group from this login, i start getting errors:
Login failed for user 'test1'
... when I login from remote server. If I login from the same host - it continues with no problem.
When I go to sql server configuration manager, I see next:
sql native client configuration(32bit):
shared memeory enabled
tcp/ip enabled
named pipes enabled
VIA disabled
The same settings from sql server 2005 network configuration / protocols for mssqlserver
sql native client configuration / client protocols
sql 2005 surface area configuration / remote connections is configured:
local and remote connections (checked), using both tcp/ip and named pipes.
Does anybody have a clue?
What is the default database for your login?
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
|||Hi Wesley
Default db is named 'test'. I made sure login has default db and can browse it.
|||Try changing the default database to master. If you can then connect with that login, there is a problem with the users access to what you were using for the default database.
-Sue
Monday, February 20, 2012
Login name is <none>
Hi,
SQL 2000. I've created a login for W2K Group Mydomain\Domain admins,
and gave it access to the DB. When I add it as a user, the login name
changes to <none>. I don't understand why. It does not happen to the
other logins.
If I am missing something basic, I would appreciate a pointer to a KB
or technet article or whatever, explaining what that is.
Thanks a lot,
PeterHi Peter,
My name is Michael and I would like to thank you for using Microsoft
newsgroup.
According to your description, I understand that you create a login in SQL
Server 2000 for domain account and add this login as a user of a specific
database. However, the login name changes to <none>. In other words, the
user in the database does not match any logins. If I have misunderstood,
please feel free to let me know.
Based on my experience, it seems that you experience the orphaned user.
Logins are associated to users by the security identifier (SID), and if the
SID is inconsistent after you move a database, SQL Server may deny the user
access to the database. This problem is known as an orphaned user.
The suggestions in the following articles should address your problem.
274188 PRB: "Troubleshooting Orphaned Users" Topic in Books Online is
Incomplete
http://support.microsoft.com/?id=274188
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
Please feel free to post in the group if this solves your problem or if you
would like further assistance.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Michael,
Thanks for the reply.
You understand the problem correctly.
I think I might have orphaned users as well, but I believe I the
answer to this particular problem which involves domain admins group
was in KB 819261
Regards,
Peter
On Wed, 14 Jan 2004 12:41:09 GMT, v-yshao@.online.microsoft.com ("Yuan
Shao") wrote:
Thanks for your feedback. Is this orphaned user problem resolved? Did you
mean you tried the workarounds mentioned in the following article and the
problem was resolved?
819261 BUG: Error 15023, 15024 or 21002 Occurs When You Try to Add a Domain
http://support.microsoft.com/?id=819261
If not, I would like you to try the suggestions(KB 274188 & KB 314546)
mentioned in my previous post to see if it fix the orphaned user problem.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||HI Michael,
Yes, this particular problem seems to be resolved by following the
workaround in that KB article, although I haven't had time to really
confirm it. Just looking at EM, it seems okay now.
What I was trying to say was I think there is a completely separate
problem with some other ophaned users and I will be looking at those
other articles next week. If they suggest using sp_change_users_login,
then please take a look on a problem I will post later on today on
with that sp in the subject.
Thanks,
Peter
On Thu, 15 Jan 2004 06:33:53 GMT, v-yshao@.online.microsoft.com ("Yuan
Shao") wrote:
SQL 2000. I've created a login for W2K Group Mydomain\Domain admins,
and gave it access to the DB. When I add it as a user, the login name
changes to <none>. I don't understand why. It does not happen to the
other logins.
If I am missing something basic, I would appreciate a pointer to a KB
or technet article or whatever, explaining what that is.
Thanks a lot,
PeterHi Peter,
My name is Michael and I would like to thank you for using Microsoft
newsgroup.
According to your description, I understand that you create a login in SQL
Server 2000 for domain account and add this login as a user of a specific
database. However, the login name changes to <none>. In other words, the
user in the database does not match any logins. If I have misunderstood,
please feel free to let me know.
Based on my experience, it seems that you experience the orphaned user.
Logins are associated to users by the security identifier (SID), and if the
SID is inconsistent after you move a database, SQL Server may deny the user
access to the database. This problem is known as an orphaned user.
The suggestions in the following articles should address your problem.
274188 PRB: "Troubleshooting Orphaned Users" Topic in Books Online is
Incomplete
http://support.microsoft.com/?id=274188
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
Please feel free to post in the group if this solves your problem or if you
would like further assistance.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Michael,
Thanks for the reply.
You understand the problem correctly.
I think I might have orphaned users as well, but I believe I the
answer to this particular problem which involves domain admins group
was in KB 819261
Regards,
Peter
On Wed, 14 Jan 2004 12:41:09 GMT, v-yshao@.online.microsoft.com ("Yuan
Shao") wrote:
quote:|||Hi Peter,
>Hi Peter,
>My name is Michael and I would like to thank you for using Microsoft
>newsgroup.
>According to your description, I understand that you create a login in SQL
>Server 2000 for domain account and add this login as a user of a specific
>database. However, the login name changes to <none>. In other words, the
>user in the database does not match any logins. If I have misunderstood,
>please feel free to let me know.
>Based on my experience, it seems that you experience the orphaned user.
>Logins are associated to users by the security identifier (SID), and if the
>SID is inconsistent after you move a database, SQL Server may deny the user
>access to the database. This problem is known as an orphaned user.
>The suggestions in the following articles should address your problem.
>274188 PRB: "Troubleshooting Orphaned Users" Topic in Books Online is
>Incomplete
>http://support.microsoft.com/?id=274188
>314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
>http://support.microsoft.com/?id=314546
>Please feel free to post in the group if this solves your problem or if you
>would like further assistance.
>Regards,
>Michael Shao
>Microsoft Online Partner Support
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and confers no rights.
Thanks for your feedback. Is this orphaned user problem resolved? Did you
mean you tried the workarounds mentioned in the following article and the
problem was resolved?
819261 BUG: Error 15023, 15024 or 21002 Occurs When You Try to Add a Domain
http://support.microsoft.com/?id=819261
If not, I would like you to try the suggestions(KB 274188 & KB 314546)
mentioned in my previous post to see if it fix the orphaned user problem.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||HI Michael,
Yes, this particular problem seems to be resolved by following the
workaround in that KB article, although I haven't had time to really
confirm it. Just looking at EM, it seems okay now.
What I was trying to say was I think there is a completely separate
problem with some other ophaned users and I will be looking at those
other articles next week. If they suggest using sp_change_users_login,
then please take a look on a problem I will post later on today on
with that sp in the subject.
Thanks,
Peter
On Thu, 15 Jan 2004 06:33:53 GMT, v-yshao@.online.microsoft.com ("Yuan
Shao") wrote:
quote:
>Hi Peter,
>Thanks for your feedback. Is this orphaned user problem resolved? Did you
>mean you tried the workarounds mentioned in the following article and the
>problem was resolved?
>819261 BUG: Error 15023, 15024 or 21002 Occurs When You Try to Add a Domain
>http://support.microsoft.com/?id=819261
>If not, I would like you to try the suggestions(KB 274188 & KB 314546)
>mentioned in my previous post to see if it fix the orphaned user problem.
>I am looking forward to hearing from you soon.
>Regards,
>Michael Shao
>Microsoft Online Partner Support
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and confers no rights.
Subscribe to:
Posts (Atom)