I'm running SQL2008R2 Dev ed. on an XP laptop. Every morning I have
to re-enter my password for SQL to start. Why would this happen? All
other functions start fine, so I know the machine in general is
connecting to the domain. Any clue?

Pete

Op 28-10-2010 17:17, Peter Cwik schreef:
Hi Pete,

The information you provide is a bit limited, so I have to do some
guesswork. But my first thought is that SQL Server starts all right, and
the password you type is to connect to SQL Server.

Background: SQL Server itself runs as a service. It is either set to
autostart, or it isn't. If it isn't, it won't prompt you for a password.
And if it is, it either starts (if the credentials stored in the
registry are still valid), or it doesn't and enters some error
information in the system log -again, it won't prompt for anything.

The architecture allows for an administrator to specify which domain
users get access to SQL Server. Therefore, you need to identify yourself
when connecting to SQL Server. You can do this in either of two ways.
Using "Windows Authentication", which means that your windows
credentials are used to log in and you don't need to type a password, or
using "SQL Server Authentication", which means you type a userid and
password that are stored in a safe place in SQL Server, and not
necessarily related to your Windows credentials.

Since a network (and even a single computer) can host multiple instances
of SQL Server, generic applications such as SQL Server Management Studio
(SSMS) will not auto-connect. You need to specify the server and SQL
Server instance you want to connect to (the last one used is already
filled in for you, and the other recent servers connected to are in the
dropdown), and choose between the two authentication methods. And if you
choose SQL Server Authentication, you'll also need to supply the userid
and password. SSMS will remember the last used SQL Server userid, and
you can also tick the box to have it remember the password.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

On Oct 28, 11:57*am, Hugo Kornelis
<h... (AT) perFact (DOT) REMOVETHIS.info.INVALID> wrote:
Thanks for the reply Hugo.
Sorry I wasn't more clear.
I do have SQL set to autostart with a domain account and yes I am an
SA in SQL and a Local Admin on my box.
On a daily basis, SQL will not autostart. It will also not start if I
try to start the service, errors with a login error. But if I go to
services and REenter my password (which has not changed) it will start
fine. My question is...why do I need to re-enter my password every
day. I'm guessing its deeper than SQL. I am an MCDBA but this one
has me stumped.
Pete

Op 28-10-2010 21:58, Peter Cwik schreef:
Hi Pete,

Wild guess - check the Windows account setting for the account SQL
Server runs under. Check that the password is set to never expire. I
have a feeling that this might be related to Windows asking the service
to change the password.

If that's not it, then check the EXACT messages in the Windows system
and/or application log. (I never remember which one to use). Maybe they
give a clue what's happening.


--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

Peter Cwik (pjcwik (AT) gmail (DOT) com) writes:
Rather than using Services, use SQL Server Configuration Manager to
configure you SQL Server services. I don't know if it matters, but
if the Configuration Manager has conflicting information about the
service account and password, maybe this is creating the mess.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) 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

On Oct 28, 2:29*pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:
Thanks for the replys.
Erland, I think your on to something there. I do remember reading
somewhere that the password should be changed in the configuration
manager, and not in Services section (though its the same password for
the same service). Something about flipping all the right switches.
The account I'm using is my own, as this is my laptop and I could
login to the domain to start the day, so I know its not an expiring
password. The silly thing started on its own today so I will keep a
watch on it.
Thanks again.
Pete

Peter Cwik (pjcwik (AT) gmail (DOT) com) writes:
Myself, I use a specific account for my SQL Services. This has two
advantages: 1) It only has the permissions it needs to have. 2) If I
change my password, the service keeps going. On my laptop, I've also
set a group policy which prevents the service account to log on
interactively.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) 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