Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SQL server decisions

  Asked By: Amolika    Date: Nov 03    Category: Sharepoint    Views: 679

We have a SQL server hardware environment on campus that is fairly
robust and figured that connecting our SPS v2 rollout to this
environment was the way to go. However, because of the rights needed by
SPS v2 to the SQL environment our SQL admin decided that he didn't want
to create a schema within the standard instance to contain the SPS data.
Instead he created a separate instance on the same servers using a
different port.

Sound good? Well, it turns out, as far as we can tell, that SPS v2
doesn't support connecting to SQLserver instances with non-standard
ports?!? So, it would seem that our only solution is going to be to
build a separate instance to handle the environment? New hardware, more
licenses, extra admin time - this seems insane to me - am I missing
anything? How are other folks connecting their SPS v2 instances to SQL



1 Answer Found

Answer #1    Answered By: Antonio Kelly     Answered On: Nov 03

You can change the port  SPS2003/WSS uses to connect to a SQL server  with
SQL Client Network Utility. You should find it from
c:\windows\system32\cliconfg.exe (or relevant path on your system). It's
fairly straightforward app -- just enable tcp/ip and click properties to
configure the port used by your SQL instance.

I can confirm several farms running very happily in non-standard SQL
ports (and actually with only data  reader/data writer rights  after
initial portal creation for extra security).

Didn't find what you were looking for? Find more on SQL server decisions Or get search suggestion and latest updates.