i think a lot of people using SQL Server 2005 Express has already used to use 'sqlcmd -S .\SQLEXPRESS' to login to the SS or using '.\SQLEXPRESS' as the Server Name to login in to the Management. but today i found that i cant login to my SS using '.\SQLEXPRESS', instead i must use the full name of my computer...that quite a long name and it's really inconvenient, could anyone help me out?
i think that the '.' in '.\SQLEXPRESS' is a short-cut for my computer name, but why i cant us it now? i was using it last week!
PS: what is the value of 'log on as' in ther property page of SQL Server 2005? i remember it is 'local service', but my current value is 'network service'
hi,
DavidShen wrote: i think a lot of people using SQL Server 2005 Express has already used to use 'sqlcmd -S .\SQLEXPRESS' to login to the SS or using '.\SQLEXPRESS' as the Server Name to login in to the Management. but today i found that i cant login to my SS using '.\SQLEXPRESS', instead i must use the full name of my computer...that quite a long name and it's really inconvenient, could anyone help me out?
i think that the '.' in '.\SQLEXPRESS' is a short-cut for my computer name, but why i cant us it now? i was using it last week!
yes... "." or "(Local)" are shorkeys for the actual local computer, and they both should run...
PS: what is the value of 'log on as' in ther property page of SQL Server 2005? i remember it is 'local service', but my current value is 'network service'
these are accounts under which the actual service is run... "network service" is more limited than "local service", but they both are way to powerfull than required... you can have a look and perhaps modify the permissions "required"..
regards
|||hi,
i can log in with 'localhost\SQLEXPRESS' or '(local)\SQLEXPRESS', but not '.\SQLEXPRESS'...really strange!! maybe there're some reg-key error, but i cant find it!!!
even though, 'localhost' and '(local)' is much shorter and easier to remember than my full computer name, i still wish to use the old way...
pllllllllllzzzzzzzzz help!
No comments:
Post a Comment