February 25, 2009 at 1:56 pm
There have been reports of it changing when SP3 was applied and I saw another post here on SSC about the latest security update. Is it a consistent thing? Can you see it change say on a regular schedule?
K. Brian Kelley
@kbriankelley
February 26, 2009 at 7:47 am
Thank you for your reply.
This was a problem even before SP3, it seems like a contant thing.
I'm not sure of the time but it seems to change back every morning around 3 am.
February 26, 2009 at 2:15 pm
Then it sounds like something is running to change it back. If it's a SQL Server 2008 server, check to see if there is a Policy that is checked at that time. If it's not, see if there is something in SQL Server Agent or whatever your job scheduler you use is to see if there is a job that changes that setting.
Also, since that setting requires a restart of SQL Server for SQL Server to pick it up, is something restarting SQL Server?
K. Brian Kelley
@kbriankelley
February 27, 2009 at 3:36 am
We are using SQL 2005 SP3.
I'll have to check the SQL server agent.
Nothing is restarting the server, setting change, but Server doesn't restart.
February 28, 2009 at 9:44 pm
If the SQL Server stays up and running, then the setting may change (and you'll still need to figure out what is causing that), but it won't take effect until SQL Server is restarted. Now are you just seeing the setting change or are you seeing the setting change and SQL Server logins start failing?
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply