October 26, 2009 at 1:39 pm
Hi I'm super new to SQL.
So far all I did was install SQL 2005 few months ago when I was installing 2003 SBS r2 server.
I'm a network admin so I have no problem working on servers/workstation etc.
The company that I'm currently working for is upgraded the current database for a software that we are using from a MDB to SQL.
Now I don't have any SQL experience at all and I'm ready to learn but there is a bit too much information for me right now.
So I was following the direction on how to update our database from MDB to SQL and there is a part in the instructions provided that says: "You must install SQL server 2005 in Mixed mode, NOT in Windows only mode."
Now I don't really know in what mode I've installed SQL 2005. So my question is, how do I find out if I have my SQL server in MIXED or WINDOWS only. Is there a way to change this after the initial installation or do I have to reinstall my SQL server.
Thanks in advance!
October 26, 2009 at 2:12 pm
Right click on the server in SSMS and click on properties. you will get the Server Properties window. Choose security and it should show what you are set for..
CEWII
October 26, 2009 at 2:25 pm
You can change it if it is not already in mixed mode. just select mixed mode in SSMS property window, OK out of it, and restart SQL (don't forget to restart SQLAgent)
---------------------------------------------------------------------
October 27, 2009 at 9:46 am
george sibbald-364359 (10/26/2009)
You can change it if it is not already in mixed mode. just select mixed mode in SSMS property window, OK out of it, and restart SQL (don't forget to restart SQLAgent)
You can change it either way, its just that going from mixed to windows only *may* have effects on applications already using the server, provided they use SQL logins, if they are using windows security already, they probably won't even notice. It is a "safer" method to go from windows only to mixed from a usability standpoint.
CEWII
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply