Re: Questions about SQL on SBS Premium



Installing a DEFAULT SQL Server instance will not affect anything in SBS
(SharePoint, Monitoring, etc.). Think of an instance as a separate "server"
within the same box. You can start-stop-restart services in this instance
without affecting the other instance. This answers your second question.
Changing the authentication from Windows to Mixed mode will not affect any
other instance. Just make sure you secure this SQL Server instance,
especially the "sa" account by using a complex pass-phrase. If you have SQL
Server Enterprise Manager installed, open the Properties page of the
defautlt SQL Server instance (should be named "local"). On the Security tab,
under the Authentication section, select SQL Server and Windows. Restart SQL
Server service after this for the changes to take effect. If you don't have
SQL Server Enterprise Manager, then you do have to tweak the registry for
this. I have a blog entry on how to do this at
http://bassplayerdoc.spaces.live.com/ (Change MSDE's authentication mode)

Let me know if you need anything else

bass_player
MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA
"Helping people grow and develop their full potential as God had plan for
them"

"Lesa H." <itsplesa@xxxxxxxxxxxxxx> wrote in message
news:evp%23W6olHHA.5084@xxxxxxxxxxxxxxxxxxxxxxx
I need a little advise from someone who knows a little more about SQL than
I do. I have a client who has SBS 2003 Premium R2 with SQL Server Workgroup
Edition and is considering a line of business application that utilizes SQL
as the back end for the software. There requirements are as follows:

1. The software needs to be installed in the Default SQL instance.

2. The authentication mode needs to be set to mixed mode (it is currently
set to Windows).

My concerns are will installing anything in the default instance of SQL
break anything in SBS (SharePoint, Monitoring, etc.), and will changing
from Windows authentication to mixed mode break anything?

Finally, how do I go about changing the authentication mode if it's not a
problem?

Thanks in advance!

Lesa H.



.



Relevant Pages

  • RE: Error installing (KB 921896)
    ... instance MSSMLBIZ ... to SQL Server. ... correct or check to see if the SQL Server Instance is set to Mixed ... the SQL Server Instance is set to Mixed Authentication ...
    (microsoft.public.windowsupdate)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... I have been using sql server for about 8 years but mainly working with sql 2000. ... know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform. ... I suggest you to check for the dynamic port number that your SQL Server graps. ... Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. ...
    (microsoft.public.sqlserver.connect)
  • Re: Installing Sql Server Express on Vista Home Premium
    ... What comes to my mind is that there is a Default SQL Server instance is installed on that working system and your application connects to that instance. ... This connection string should work as you do not force the connection to use a specific protocol, Shared Memory will be used as this is the primary protocol by default. ... Default Instances uses 1433 TCP port by default as a Static Port but not the ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server 2005 and security patch issues?
    ... I guess the problem occurs while you are trying to log in to your SQL Server instance, if so, do you get any error message? ... I recreated a fresh instance and a fresh copy of the ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... Will you show me the Connection String you use for your application to connect to your remote SQL Server instance? ... I suggest you to check for the dynamic port number that your SQL Server graps. ...
    (microsoft.public.sqlserver.connect)