Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-sqlserver > #356 > unrolled thread

SQL 2008 Best Practices

Back to article view | Back to comp.databases.ms-sqlserver

Contents

  SQL 2008 Best Practices "Bob Barrows" <reb01501@NOyahooSPAM.com> - 2011-05-19 14:56 -0400
    Re: SQL 2008 Best Practices Erland Sommarskog <esquel@sommarskog.se> - 2011-05-19 23:42 +0200

#356 — SQL 2008 Best Practices

Well, we've finally set up a new server and installed 2008 on it (Denali?
What's that?). Anyway, I hit my first hurdle: Integration Services would not
start - "failed to respond in a timely fashion".
I checked the Log On tab on the Services Property dialog and noted that it
was set to log on with an account called "NETWORK SERVICE", with obscured
passwords, of course. I clicked the "Local System Account" radio button and
tried again. This time the service started with no problem. But now I'm
wondering if that's a good setting. I checked our current SQL 2005 servers
and they are set to run under the local system account as well, but that
means nothing - they were installed before my time. I realize that SQL
Server itself should be using a domain account - does this advice apply to
integration services too? If not, what is the recommendation?

Bob

[toc] | [next] | [standalone]

#359

Bob Barrows (reb01501@NOyahooSPAM.com) writes:
> Well, we've finally set up a new server and installed 2008 on it
> (Denali? What's that?). Anyway, I hit my first hurdle: Integration
> Services would not start - "failed to respond in a timely fashion". I
> checked the Log On tab on the Services Property dialog and noted that it 
> was set to log on with an account called "NETWORK SERVICE", with
> obscured passwords, of course. I clicked the "Local System Account"
> radio button and tried again. This time the service started with no
> problem. But now I'm wondering if that's a good setting. I checked our
> current SQL 2005 servers and they are set to run under the local system
> account as well, but that means nothing - they were installed before my
> time. I realize that SQL Server itself should be using a domain account
> - does this advice apply to integration services too? If not, what is
> the recommendation? 
 
It seems that I have Integration Services running under Network Service 
on my box. I think I had problems with getting SSIS to start on when 
I booted the machine, this was also true for the Database Engine.

I believe I resolved this issue when I finally learned to spell to 
ServicesPipeTimeout. (That's a registry key.)

But I don't use SSIS much at all, since I don't know it.

-- 
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.ms-sqlserver

csiph-web