HelpSQL Agent Security

We have sensitive data that requires the builtin\administrators group be removed so domain admins are unable to see data. When we do this, SQL can continue to run under the local system account, but the SQL Agent cannot.

Does anyone else have a solution that will lockout NT admins (both local and domain) and allow both SQL and the SQL AGENT to run properly?

TIA

Ryan HuntDid you give the new domain account sysadmin rights?

And configure it to start with that account?|||Thanks for the response. I ended up just creating a local admin account for the agent with specific SA rights to the server. Then, had the only department allowed to have access to the data change the password. This seems like the best choice...

Thanks

HELP:SQL Port lost or never set on new install

I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility
.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:

> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utili
ty.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote:
>

HELP:SQL Port lost or never set on new install

I just installed SQL Server on XP (SP2) attempted to access the Server
through JDBC and got a error abut the socket connect. After much searching I
find that the port is not active even though all app that would set the port
have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc. SQL
service is running in the tasklist but the port doesn't show in netstat.
I turned all firewalls off, disconnected the internet and still no port. The
problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
remote access turned off by default
http://msdn2.microsoft.com/en-us/library/ms178763.aspx
is SQL2k check the SQL Errorlog \ Windows Application for Errors
cheers,
Andy.
"jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>I just installed SQL Server on XP (SP2) attempted to access the Server
> through JDBC and got a error abut the socket connect. After much searching
> I
> find that the port is not active even though all app that would set the
> port
> have port 1433 set. If you follow. I ran netstat -ano and tasklist /svc.
> SQL
> service is running in the tasklist but the port doesn't show in netstat.
> I turned all firewalls off, disconnected the internet and still no port.
> The
> problem doesn't seem to be with the Firewall but XP SP2 & SQLServer.
>
|||The errorlog has it listening on Shared Memory, & Named Pipes even though
Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
I tried to scrambble the protocols by disabling and restarting the server,
but the TCP/IP protocol doesn't show.
"Andy Ball" wrote:

> its not SQL Server 2005 is it ? Most versions (Dev, Express, Eval) have
> remote access turned off by default
> http://msdn2.microsoft.com/en-us/library/ms178763.aspx
> is SQL2k check the SQL Errorlog \ Windows Application for Errors
> cheers,
> Andy.
>
> "jlopes151" <jlopes151@.discussions.microsoft.com> wrote in message
> news:363D1BB3-69C2-49E3-A77B-660117628D48@.microsoft.com...
>
>
|||Problem solved with the SP4 update.
"jlopes151" wrote:
[vbcol=seagreen]
> The errorlog has it listening on Shared Memory, & Named Pipes even though
> Named Pipes & TCP/IP protocols are enabled in the SQL Network Server Utility.
> I tried to scrambble the protocols by disabling and restarting the server,
> but the TCP/IP protocol doesn't show.
> "Andy Ball" wrote: