|
| | | 
StrataFrame User
 
Group: StrataFrame Users
Last Login: 07/09/2008 2:20:16 PM
Posts: 436, Visits: 944 |
| I'm bringing up our first SQL Server 2005 production server. Does anybody have any advice as to what to watch out for, what not to do, what to do, etc...
I'm just nervous and want to make sure all my bases are covered... its 10 times harder to make changes once we release this server into production.
Thanks ;-) |
| |
| | | 
StrataFrame Developer
Group: StrataFrame Developers
Last Login: 10/21/2008 9:20:58 AM
Posts: 2,685, Visits: 1,887 |
| Not really any gotchas... just make sure that you have the authentication option set right from the get go... i.e.: if you want SQL Server auth to be enabled (so you can use "sa" or whatever), then it's much easier to enable it through the install than it is once it's up (as you mentioned). Other than that, we let pretty much everything stay at the default.
www.bungie.net |
| |
| | | 
Advanced StrataFrame User
Group: StrataFrame Users
Last Login: Today @ 5:18:40 AM
Posts: 658, Visits: 26,201 |
| | I have done a few SQL 2005 production deploys now and I agree to leave most of the defaults, that and don't forget to turn on TCP/IP (hehe I did that my first TWO times), LOL. |
| |
| | |
StrataFrame Developer
Group: StrataFrame Developers
Last Login: 10/21/2008 9:20:58 AM
Posts: 2,685, Visits: 1,887 |
| Aye, good point, Keith... TCP/IP is not enabled by default on SQL Server Express. You have to go into the Configuration Manager, enable it, then restart the service. It is, however, enabled by default on the full version of SQL Server 2005 (Workgroup & up, the ones you have to pay for  ).
www.bungie.net |
| |
|
|