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 instances

config - 2 machines in a workgroup, service running under local system account. Tried the following config. from Rushi. Running profiles on both machines. on source - starts the conversation, and a send. then get an event subclass 2-remote at a periodic interval (in a loop), no activty on the other end. any suggestions
In master:
1. Create master key for database 'master'.
2. Create certificate for user 'dbo' in database 'master'.
3. Create service broker endpoint using certificate created above.
4. Grant connect on above endpoint to the login 'Public'.

In your database:
1. Create master key.
2. Grant send on target service to user 'public'.
3. Create routes to initiator services on other servers.
4. Create routes to target services on other servers.

Now begin dialog with encryption = off and send.
It could be an incorrect address used in the route (a typo in the DNS name), a port number mismatch between the route and the endpoint configuration, a port being blocked by personal firewall, IPSEC blocking a TCP connection etc. What is the value of transmission_status column in the sys.transmission_queue view in the initiatr database?

Have you tried using the service listing stored procs from Rushi's site? They make this kind of tasks much easier.

Regards,
~ Remus|||The service listings stored procs are now available on our CodeGallery:

http://www.gotdotnet.com/codegallery/codegallery.aspx?id=9f7ae2af-31aa-44dd-9ee8-6b6b6d3d6319
Later,

Rushi