remotely start/stop sql server service in a workgroup

hi, i have an administrator account on a box, there is a sql server pc
in the same workgroup w/ a different admin pass (which i know ^_^, and
the sql sa pass too), how can i restart the sql server service from my box ?You can use xp_cmdshell with NET START/STOP MSSQLSERVER command. On you
command prompt type in NET START /? for details on this DOS command. For
details on xp_cmdshell, refer to SQL Server Books Online.
Anith|||Anith Sen wrote:
> You can use xp_cmdshell with NET START/STOP MSSQLSERVER command. On you
> command prompt type in NET START /? for details on this DOS command. For
> details on xp_cmdshell, refer to SQL Server Books Online.
>
xp_cmdshell is deleted(as recomended by every sql server security
quide), i can kill the process using pskill, but could that lead to data
loss?|||You can stop using the TSQL SHUTDOWN command.
At the OS level, you can both start and stop using NETSVC.EXE (Google for it
).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Fred" <fred@.ilovespam.com> wrote in message news:exFBLGgHGHA.2036@.TK2MSFTNGP14.phx.gbl...[
color=darkred]
> hi, i have an administrator account on a box, there is a sql server pc
> in the same workgroup w/ a different admin pass (which i know ^_^, and
> the sql sa pass too), how can i restart the sql server service from my box ?[/colo
r]

Remote SSIS Access

Hello,
We have discovered that unless a user is an administrator on the MS SQL 2005
server, they cannot connect to SSIS server locally or remotely.
The SQL Junkies site has the solution. They recommend that you first add the
user to the Distributed COM Users group. Then you should run
%windir%\system32\Com\comexp.msc to launch Component Services to launch
component server. On the properties of MsDtsServer you can choose security
and from there you can set the Remote Activation permissions to allow the
user to connect the SSIS server remotely. The SSIS service should then be
restarted.
I tried it and it works. However, what are the security implications with
this solution?The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:

>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>|||The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:

>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>

Remote Server login

I got a problem a system administrator can not log on to sql remote server so he can back up the system tables. Hes doing it through active directory, not sure what the problem is. can anyone help please. reason says not associated with a trusted sql connection?Is Builtin Administrators group registered with the server with sysadmin server role? And if not, is the server configured for Mixed Security Mode? How is your admin trying to connect?|||hes logging in through windows only, not in mix mode|||Then you need to look into what account he uses and if that account is explicitly present in the Logins of the server or if its group is present there. I'd make sure that Builtins is in the logins and tell him that he should fix it himself, - include Domain Admins or his account into Local Administrators group (Builtin Administrators).|||Actually, if the BUILTIN/Administrators group is not part of SQL Server, that's a good thing. The DBA group should be the ONLY group with sysadmin rights on SQL Servers. The Domain Admins should be allowed backup permissions if that's part of their job description. Normally, the DBA does that also though.|||Well, not if you're doing replication.|||Well, I doubt they're doing replication if they can't even figure out how to log into a box. Codd, what were you thinking?|||Hey, you know we're talking about Brett here (wink-wink), Codd knows what he does there...between margaritas... :D...I'm loosing my mind...OF COURSE IT'S a WRONG THREAD!!! Oh well, eventually Brett will show up and say what I thought he already did...How many of those shots did I have?