Showing posts with label login. Show all posts
Showing posts with label login. Show all posts

Thursday, March 29, 2012

Draging and Droping scripts

I just upgraded from SQL2000 to SQL 2005. When I have a query opened for a database already and I want to drag and drop a script in, I get the login box. Is there anyway to get this to not happen? I would like it that when I drag and drop the script it is just loaded in a new query with the database connection that I was using already. (This is what it did in SQL2000) Thanks.

Right-click on the database in question in the object explorer and select "New Query".

Buck Woody

Draging and Droping scripts

I just upgraded from SQL2000 to SQL 2005. When I have a query opened for a database already and I want to drag and drop a script in, I get the login box. Is there anyway to get this to not happen? I would like it that when I drag and drop the script it is just loaded in a new query with the database connection that I was using already. (This is what it did in SQL2000) Thanks.

Right-click on the database in question in the object explorer and select "New Query".

Buck Woody

Drag and drop query onto Management Studio

Everytime I drag and drop a query file (.sql) from Windows Explorer onto
Management Studio, I am prompted to login. How do I get drag and drop to use
existing connection?
guy,
Install SP2 I believe. (At least it works for me.)
RLF
"guy" <guy@.hotmail.com> wrote in message
news:OiHKPyJqHHA.4872@.TK2MSFTNGP03.phx.gbl...
> Everytime I drag and drop a query file (.sql) from Windows Explorer onto
> Management Studio, I am prompted to login. How do I get drag and drop to
> use existing connection?
>
|||That"s the ticket. Thank you.
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:OGnQpwRqHHA.3740@.TK2MSFTNGP02.phx.gbl...
> guy,
> Install SP2 I believe. (At least it works for me.)
> RLF
> "guy" <guy@.hotmail.com> wrote in message
> news:OiHKPyJqHHA.4872@.TK2MSFTNGP03.phx.gbl...
>

Monday, March 19, 2012

Doubling up security on SQL Server system administrator

Hi All
Always baffled me this, but although I can set up complex SQL usernames and
passwords for my SQL database the main system administrator login details
only give me half the security because the username is always 'sa'. I can
only set a complex password for the most powerful user of them all.
This might be a very newbie question, but is it possible (and advisable -
knowing Microsoft's progs don't like changing core settings after the event)
to change the system admin's username to something else?
Please note that I already have a number of databases running on this SQL
server installation so would this implicate their use if I changed it?
Rgds
RobbieSee reply in .setup
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Astra" <info@.NoEmail.com> wrote in message
news:eqYQsd%239EHA.2680@.TK2MSFTNGP09.phx.gbl...
> Hi All
> Always baffled me this, but although I can set up complex SQL usernames
> and
> passwords for my SQL database the main system administrator login details
> only give me half the security because the username is always 'sa'. I can
> only set a complex password for the most powerful user of them all.
> This might be a very newbie question, but is it possible (and advisable -
> knowing Microsoft's progs don't like changing core settings after the
> event)
> to change the system admin's username to something else?
> Please note that I already have a number of databases running on this SQL
> server installation so would this implicate their use if I changed it?
> Rgds
> Robbie
>|||Robbie,
Did you ever get the answer to this? I want to do the same as you -
how do I do it?
Darren.
Astra wrote:
> *Hi All
> Always baffled me this, but although I can set up complex SQL
> usernames and
> passwords for my SQL database the main system administrator login
> details
> only give me half the security because the username is always 'sa'.
> I can
> only set a complex password for the most powerful user of them all.
> This might be a very newbie question, but is it possible (and
> advisable -
> knowing Microsoft's progs don't like changing core settings after the
> event)
> to change the system admin's username to something else?
> Please note that I already have a number of databases running on this
> SQL
> server installation so would this implicate their use if I changed
> it?
> Rgds
> Robbie *
railex
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1342852.html

Sunday, February 26, 2012

DomainUserAccount?

Is there any PROC or variable that can tell me what the domain login name is
of the user asking for data from SQL server?
reg.
Kjell BrandesCheck out SUSER_SNAME() in the BOL.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
.
"Kjell Brandes" <kjell@.brandes.tv> wrote in message
news:OQdF9kGMFHA.2748@.TK2MSFTNGP09.phx.gbl...
Is there any PROC or variable that can tell me what the domain login name is
of the user asking for data from SQL server?
reg.
Kjell Brandes

DOMAIN\REMOTE_MACHINE_NAME$ account

does anyone know under what circumstances a SQL Server login from
code/services running on a remote server would be attempted using an account
named DOMAIN\REMOTE_MACHINE_NAME$ where REMOTE_MACHINE_NAME is the machine
where the code is running (and of course failing) ...
specifically i am talking about a call to a WebStore web service that then
makes the call to SQL Server, where the service has been configured to use a
specific domain account (that usually is utilized and works)When the code on the remote machine is running under a local security
context (like LocalSystem, Network Service, Local Service etc) would be the
most common scenario.
Cheers
Ken
Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com
"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:uKiQujSRFHA.3544@.TK2MSFTNGP12.phx.gbl...
: does anyone know under what circumstances a SQL Server login from
: code/services running on a remote server would be attempted using an
account
: named DOMAIN\REMOTE_MACHINE_NAME$ where REMOTE_MACHINE_NAME is the machine
: where the code is running (and of course failing) ...
:
: specifically i am talking about a call to a WebStore web service that then
: makes the call to SQL Server, where the service has been configured to use
a
: specific domain account (that usually is utilized and works)
:
:

Domain Trust - login failed: not a trusted sql connection

(Cross post from newsgroup)

Attempting to implement Windows authentication between trusted domains. . .

I have a domain trust set up between two domains connected via persistent vpn:
REMOTE and HQ

sqlserv is: HQ\SQLSERV (SQL 2000 server)

client machine is: REMOTE\MACHINE1 (SQL 2005 tools)

I sucessfully added user REMOTE\User1 to system admins on HQ\SQLSERV I can login via Remote Desktop from REMOTE\MACHINE1 to HQ\SQLSERV and open SQL2000 Query Analyzer and query databases as REMOTE\User1

When running SQL2005 SQL Server Management Server on REMOTE\MACHINE1 logged on as REMOTE\User1
I cannot connect to HQ\SQLSERV.
I get:

TITLE:
Connect to Server
Cannot connect to HQ\SQLSERV.
ADDITIONAL INFORMATION: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
BUTTONS: OK

Any ideas? What I am trying to do should be possible. Isn't it?

Check your connection info in SSMS on REMOTE\MACHINE1
Check you have all the required DNS
Try osql -SSQLSERV -E|||

Mulhall wrote:

Check your connection info in SSMS on REMOTE\MACHINE1


fails on both named pipes and tcp/ip


Check you have all the required DNS


It appears the DNS replicates sucessfully as I have set up secondaries on both sides for the other domains.
I can ping from one side to the other.
I can assign rights from one side to the other, etc. . .


Try osql -SSQLSERV -E

same error|||

Ahhh. . .

found the problem. . .

forgot that we had moved all of our workstations into sets of ADS folders, one for general all purpose use where access via network was permitted to all authenticated users and one set that had access permissions specifically defined to only developers.

Had to give access to the remote developers group via group policy.
The easiest thing was -

Add a Local Domain Group on HQ - Remote Developers
Add REMOTE\Developers to HQ\Remote Developers
Add HQ\Remote Developers to 'Allow access from network' on the applicable gpo

Does that make sense?

Well, it works!!!

You know. . .
Somethings M$ does really really well - Active Directory/Policy Management/Name Service Administration, SQL Server!!!

Somethings they choke on - Visual Studio 6 (oh what a dog!)

At any rate, setting up this VPN and Domain trust was rather simple and straight forward!

Friday, February 24, 2012

Domain not visible

I just upgraded my 2000 installation to Sql Server 2005 Developer. When I try to create a new login I can only use local accounts. Search and the Locations only displays the computer name and not the domain. Any help would be greatly appreciated,

Robert van Poelgeest

Hi Robert - I assume you are using SSMS but correct me if I'm wrong.

Are you running SSMS (client) on the same machine as the Server?

Are you logged into client machine with a domain account from domain you want to add?

Can you add the desired domain account using the CREATE LOGIN command?

|||

Hi Bruce,

Yes I am using SSMS on the server itself and yes I am logged in using a domain account. I haven't tried using a CREATE LOGIN account but I will.

update: This whole problem was caused by a dns configuration problem and was not caused by anything in Sqlserver

domain local group in SQL 2000

Does anybody know if you can add the domain local group in
the SQL 2000 login? Please note "domain local group" not
the local group.
Jennifer"Jennifer @. Oxnard" <anonymous@.discussions.microsoft.com> wrote in message
news:024a01c3aade$8dd69da0$a301280a@.phx.gbl...
> Does anybody know if you can add the domain local group in
> the SQL 2000 login? Please note "domain local group" not
> the local group.
I just answered that in *.security
Steve

Domain group server access?

Hi,
If a user needs access to a databases and I carry out the following steps:
1) Create a domain group
2) Put the users login details in this group
3) Give the domain group access to SQL Server via Enterprise Manager
4) Give the domain group database access via Enterprise Manager
Do I also need to give this domain group direct server access by adding it
to a group in:
Computer Management\Local Users and Groups\Groups ?
Ta
wendyalso, we are using active directory.
wendy
"Woo" wrote:

> Hi,
> If a user needs access to a databases and I carry out the following steps:
> 1) Create a domain group
> 2) Put the users login details in this group
> 3) Give the domain group access to SQL Server via Enterprise Manager
> 4) Give the domain group database access via Enterprise Manager
> Do I also need to give this domain group direct server access by adding it
> to a group in:
> Computer Management\Local Users and Groups\Groups ?
> Ta
> wendy|||No you don't need to give OS level permissions on the server
that is running SQL Server for the group to access SQL
Server. You only need to add the windows group to the SQL
Server logins (and whatever databases).
-Sue
On Fri, 3 Nov 2006 04:14:02 -0800, Woo
<Woo@.discussions.microsoft.com> wrote:

>Hi,
>If a user needs access to a databases and I carry out the following steps:
>1) Create a domain group
>2) Put the users login details in this group
>3) Give the domain group access to SQL Server via Enterprise Manager
>4) Give the domain group database access via Enterprise Manager
>Do I also need to give this domain group direct server access by adding it
>to a group in:
>Computer Management\Local Users and Groups\Groups ?
>Ta
>wendy|||And you will have to give the windows group permissions to access tables,
views, stored procedures, etc.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:bcjmk2h4eoundvep74genb5d43ldjveog2@.
4ax.com...
> No you don't need to give OS level permissions on the server
> that is running SQL Server for the group to access SQL
> Server. You only need to add the windows group to the SQL
> Server logins (and whatever databases).
> -Sue
> On Fri, 3 Nov 2006 04:14:02 -0800, Woo
> <Woo@.discussions.microsoft.com> wrote:
>
>

Sunday, February 19, 2012

Domain and windows authentication

Hi,
We have a application that uses windows authentication to connect to sql
server. We have a domain and simply just create a login in sql server for
each user in the domain.
We have setup this application in the company that doesn't have domain.
We're not going to change the source of the application to accept sql server
authentication.
Can we still use the windows authentication to allow the users to log in?
Suppose that each user logs in his computer as administrator of that
computer. Can we prefix these administrators with the name of their
computers to create login in sql server and still use windows
authentication?
Any help would be greatly appreciated.
Amin
Microsoft SQL Server support only Domain Authentification, no Machine
Account Authentification (except the local machine of the sql server),
because Workgroups are not trustable.
Hope this helps,
Jens Smeyer
"Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a application that uses windows authentication to connect to sql
> server. We have a domain and simply just create a login in sql server for
> each user in the domain.
> We have setup this application in the company that doesn't have domain.
> We're not going to change the source of the application to accept sql
server
> authentication.
> Can we still use the windows authentication to allow the users to log in?
> Suppose that each user logs in his computer as administrator of that
> computer. Can we prefix these administrators with the name of their
> computers to create login in sql server and still use windows
> authentication?
> Any help would be greatly appreciated.
> Amin
>
|||Jens,
Therefore in workgroups there's no other solution except using sql server
authentication?
"Jens Smeyer" <MrIgel[RejectSpam|RemoveBracket]@.gmx.de> wrote in message
news:OCvmQg7gEHA.2764@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Microsoft SQL Server support only Domain Authentification, no Machine
> Account Authentification (except the local machine of the sql server),
> because Workgroups are not trustable.
> Hope this helps,
> Jens Smeyer
>
> "Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
> news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
for[vbcol=seagreen]
> server
in?
>
|||You should be able to use NT authentication by doing the following:
1. Create a local account on the SQL Server machine that matches each
individual users local machine account. Make sure the password is the same
for both accounts.
2. Create a login within SQL Server for each of these logins.
3. NT authentication should now work.
This could be difficult to administer becaues each time a user changes his
local opassword the pasword has to be changed at the SQL Server machine as
well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Rand,
What if users log into their computer with administrator account?
Necessarily they must use different user names?
Amin
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:Qxq9sH9gEHA.3340@.cpmsftngxa06.phx.gbl...
> You should be able to use NT authentication by doing the following:
> 1. Create a local account on the SQL Server machine that matches each
> individual users local machine account. Make sure the password is the same
> for both accounts.
> 2. Create a login within SQL Server for each of these logins.
> 3. NT authentication should now work.
> This could be difficult to administer becaues each time a user changes his
> local opassword the pasword has to be changed at the SQL Server machine as
> well.
> Rand
>
> This posting is provided "as is" with no warranties and confers no rights.
>

Domain and windows authentication

Hi,
We have a application that uses windows authentication to connect to sql
server. We have a domain and simply just create a login in sql server for
each user in the domain.
We have setup this application in the company that doesn't have domain.
We're not going to change the source of the application to accept sql server
authentication.
Can we still use the windows authentication to allow the users to log in?
Suppose that each user logs in his computer as administrator of that
computer. Can we prefix these administrators with the name of their
computers to create login in sql server and still use windows
authentication?
Any help would be greatly appreciated.
AminMicrosoft SQL Server support only Domain Authentification, no Machine
Account Authentification (except the local machine of the sql server),
because Workgroups are not trustable.
Hope this helps,
Jens Süßmeyer
"Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a application that uses windows authentication to connect to sql
> server. We have a domain and simply just create a login in sql server for
> each user in the domain.
> We have setup this application in the company that doesn't have domain.
> We're not going to change the source of the application to accept sql
server
> authentication.
> Can we still use the windows authentication to allow the users to log in?
> Suppose that each user logs in his computer as administrator of that
> computer. Can we prefix these administrators with the name of their
> computers to create login in sql server and still use windows
> authentication?
> Any help would be greatly appreciated.
> Amin
>|||Jens,
Therefore in workgroups there's no other solution except using sql server
authentication?
"Jens Süßmeyer" <MrIgel[RejectSpam|RemoveBracket]@.gmx.de> wrote in message
news:OCvmQg7gEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server support only Domain Authentification, no Machine
> Account Authentification (except the local machine of the sql server),
> because Workgroups are not trustable.
> Hope this helps,
> Jens Süßmeyer
>
> "Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
> news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> > We have a application that uses windows authentication to connect to sql
> > server. We have a domain and simply just create a login in sql server
for
> > each user in the domain.
> > We have setup this application in the company that doesn't have domain.
> > We're not going to change the source of the application to accept sql
> server
> > authentication.
> > Can we still use the windows authentication to allow the users to log
in?
> > Suppose that each user logs in his computer as administrator of that
> > computer. Can we prefix these administrators with the name of their
> > computers to create login in sql server and still use windows
> > authentication?
> > Any help would be greatly appreciated.
> > Amin
> >
> >
>|||You should be able to use NT authentication by doing the following:
1. Create a local account on the SQL Server machine that matches each
individual users local machine account. Make sure the password is the same
for both accounts.
2. Create a login within SQL Server for each of these logins.
3. NT authentication should now work.
This could be difficult to administer becaues each time a user changes his
local opassword the pasword has to be changed at the SQL Server machine as
well.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand,
What if users log into their computer with administrator account?
Necessarily they must use different user names?
Amin
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:Qxq9sH9gEHA.3340@.cpmsftngxa06.phx.gbl...
> You should be able to use NT authentication by doing the following:
> 1. Create a local account on the SQL Server machine that matches each
> individual users local machine account. Make sure the password is the same
> for both accounts.
> 2. Create a login within SQL Server for each of these logins.
> 3. NT authentication should now work.
> This could be difficult to administer becaues each time a user changes his
> local opassword the pasword has to be changed at the SQL Server machine as
> well.
> Rand
>
> This posting is provided "as is" with no warranties and confers no rights.
>

Domain and windows authentication

Hi,
We have a application that uses windows authentication to connect to sql
server. We have a domain and simply just create a login in sql server for
each user in the domain.
We have setup this application in the company that doesn't have domain.
We're not going to change the source of the application to accept sql server
authentication.
Can we still use the windows authentication to allow the users to log in?
Suppose that each user logs in his computer as administrator of that
computer. Can we prefix these administrators with the name of their
computers to create login in sql server and still use windows
authentication?
Any help would be greatly appreciated.
AminMicrosoft SQL Server support only Domain Authentification, no Machine
Account Authentification (except the local machine of the sql server),
because Workgroups are not trustable.
Hope this helps,
Jens Smeyer
"Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> We have a application that uses windows authentication to connect to sql
> server. We have a domain and simply just create a login in sql server for
> each user in the domain.
> We have setup this application in the company that doesn't have domain.
> We're not going to change the source of the application to accept sql
server
> authentication.
> Can we still use the windows authentication to allow the users to log in?
> Suppose that each user logs in his computer as administrator of that
> computer. Can we prefix these administrators with the name of their
> computers to create login in sql server and still use windows
> authentication?
> Any help would be greatly appreciated.
> Amin
>|||Jens,
Therefore in workgroups there's no other solution except using sql server
authentication?
"Jens Smeyer" <MrIgel[RejectSpam|RemoveBracket]@.gmx.de> wrote in messa
ge
news:OCvmQg7gEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Microsoft SQL Server support only Domain Authentification, no Machine
> Account Authentification (except the local machine of the sql server),
> because Workgroups are not trustable.
> Hope this helps,
> Jens Smeyer
>
> "Amin Sobati" <amins@.morva.net> schrieb im Newsbeitrag
> news:%23ahXq45gEHA.1764@.TK2MSFTNGP10.phx.gbl...
for[vbcol=seagreen]
> server
in?[vbcol=seagreen]
>|||You should be able to use NT authentication by doing the following:
1. Create a local account on the SQL Server machine that matches each
individual users local machine account. Make sure the password is the same
for both accounts.
2. Create a login within SQL Server for each of these logins.
3. NT authentication should now work.
This could be difficult to administer becaues each time a user changes his
local opassword the pasword has to be changed at the SQL Server machine as
well.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand,
What if users log into their computer with administrator account?
Necessarily they must use different user names?
Amin
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:Qxq9sH9gEHA.3340@.cpmsftngxa06.phx.gbl...
> You should be able to use NT authentication by doing the following:
> 1. Create a local account on the SQL Server machine that matches each
> individual users local machine account. Make sure the password is the same
> for both accounts.
> 2. Create a login within SQL Server for each of these logins.
> 3. NT authentication should now work.
> This could be difficult to administer becaues each time a user changes his
> local opassword the pasword has to be changed at the SQL Server machine as
> well.
> Rand
>
> This posting is provided "as is" with no warranties and confers no rights.
>

Domain account without a SQL login account

I have a situation that I have discovered in our QA database that I need to resolve. When I looked at the Activity Monitor for our server, I discovered that a process is running under a domain user account for one of our .Net applications. The problem is that that domain user account has not been created as a SQL login account on the server. I am trying to figure out how someone can log in to the database server with a domain user account that has not been added to SQL Server as a login account.

Does anyone have any insight on this? I don't like the idea of someone being able to create domain account that can access the database without me granting them specific access.

- Larry

It could be working under the guest account, it could be included in a domain group account that has database access, it could be under an ALIAS (a deprecated feature -and still dangerous).|||

Most likely the Windows user has permission to connect via a Windows group membership. If the user belongs to one or more of such group and it has CONNECT SERVER permission, the Windows user will have access to connect to SQL Server.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Apparently, the account in question was a member of the WIndows local admin group. It makes me rather nervous that an ID could be created that basically has unlimited access to my databases and, as the DBA, I can't do a whole lot about this. Is there a good way that I can mitigate this risk?

|||

Here is a link to a different forum question on how to remove local administrators from the sysadmin group. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1559584&SiteID=1

Be aware that this helps to keep honest people honest and prevent misuse by mitake, but it is only a speed-bump in case the machine administrator is truly malicious and determined to get to your data. As the machine administrator has full control over the machine and files stored there as well as any process running on it. I would strongly recommend a establishing a security policy so you can monitor and audit activity on both SQL Server as well as on the machine itself.

-Raul Garcia

SDE/T

SQL Server Engine

Dollar sign behind user name

What does the $ (dollar sign) means behind the SQL Server login?
I had a SQL Server login something like this "DomainName\User$".
Peter ChanThis is generally a computer account. If a service runs under Local System
or Network Service on a remote computer it can be allowed access to SQL
across the network via it's computer account (which is the credential it
passes over the network)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
http://sqlblogcasts.com/blogs/sqldbatips
"wodoy.peter" <wodoy.peter@.gmail.com> wrote in message
news:1175854131.654355.132230@.y80g2000hsf.googlegroups.com...
> What does the $ (dollar sign) means behind the SQL Server login?
> I had a SQL Server login something like this "DomainName\User$".
>
> Peter Chan
>

Dollar sign behind user name

What does the $ (dollar sign) means behind the SQL Server login?
I had a SQL Server login something like this "DomainName\User$".
Peter ChanThis is generally a computer account. If a service runs under Local System
or Network Service on a remote computer it can be allowed access to SQL
across the network via it's computer account (which is the credential it
passes over the network)
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
http://sqlblogcasts.com/blogs/sqldbatips
"wodoy.peter" <wodoy.peter@.gmail.com> wrote in message
news:1175854131.654355.132230@.y80g2000hsf.googlegroups.com...
> What does the $ (dollar sign) means behind the SQL Server login?
> I had a SQL Server login something like this "DomainName\User$".
>
> Peter Chan
>