Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 18,330 of 19,505    |
|    Bob Barrows to All    |
|    SQL 2008 Best Practices    |
|    19 May 11 14:56:00    |
      From: reb01501@NOyahooSPAM.com              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              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca