Best Security Template for a Member Server level SQL server install

This does not seem like rocket science but I can't find a recommendation
from MS on which uplevel (from defaults) Security Template (file server,
infrastructure server, etc.) is the best baseline starting point for a SQL
install on a W2K3 AD. I realize that mods will be necessary no matter but
since there are 700+ settings having a head start seems like a good thing. I
have created the OU specifically for the SQL server and just need to
configure it's GP including IPSec. I have implemented most of the suggested
Security settings to the install of SQL itself (see prior post).
Any suggestions?
ThanksThe Enterprise - Member Server Template is the template that should be
used. Also, generate a rollback template to help you with your testing.
The High Security Template should not be used.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Best practice for maintenance plans

Hi,
with SQL 2k the maintenance plan wizard proposed defaults for all
maintenance tasks. With SQL 2005 this is gone.
What are the best practices to setup a "normal" SQL 2005 maintenance?
Thanks for any advice
Greg
--
Greg JimsonHi Greg,
You should be installed SSIS (Integration Service) to be able to use it, or
just to install Service Packets would be enough as well.
Maintenance still stands in the Management node in SQL Server 2005. Go to
Maintenance Plans and right click on it.
Click Maintenance Plan Wizard.
--
Ekrem Önsoy
"Greg Jimson" <nospam@.hotmail.com> wrote in message
news:%23rL5E1T7HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Hi,
> with SQL 2k the maintenance plan wizard proposed defaults for all
> maintenance tasks. With SQL 2005 this is gone.
> What are the best practices to setup a "normal" SQL 2005 maintenance?
> Thanks for any advice
> Greg
> --
> Greg Jimson
>|||Hi Ekrem,
thanks for you answer. May I specify my question. What Task need to be
setup? Shrink, History Clean up, etc.?
Thanks in advance
Greg
--
Greg Jimson
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:147C4862-4C46-48F8-8440-4A2AB441AFDE@.microsoft.com...
> Hi Greg,
>
> You should be installed SSIS (Integration Service) to be able to use it,
> or just to install Service Packets would be enough as well.
> Maintenance still stands in the Management node in SQL Server 2005. Go to
> Maintenance Plans and right click on it.
> Click Maintenance Plan Wizard.
> --
> Ekrem Önsoy
>
>
> "Greg Jimson" <nospam@.hotmail.com> wrote in message
> news:%23rL5E1T7HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> with SQL 2k the maintenance plan wizard proposed defaults for all
>> maintenance tasks. With SQL 2005 this is gone.
>> What are the best practices to setup a "normal" SQL 2005 maintenance?
>> Thanks for any advice
>> Greg
>> --
>> Greg Jimson
>|||It depends on what you want to do and your needs.
In the "Select Maintenance Tasks" window at the bottom side you will see the
description box which describes each option when you click on them.
For instance, you schedule "Maintenance Cleanup Task" to remove files left
over from executing a maintenance plan.
--
Ekrem Önsoy
MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT
"Greg Jimson" <nospam@.hotmail.com> wrote in message
news:eqHkn4V7HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Hi Ekrem,
> thanks for you answer. May I specify my question. What Task need to be
> setup? Shrink, History Clean up, etc.?
> Thanks in advance
> Greg
> --
> Greg Jimson
> "Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
> news:147C4862-4C46-48F8-8440-4A2AB441AFDE@.microsoft.com...
>> Hi Greg,
>>
>> You should be installed SSIS (Integration Service) to be able to use it,
>> or just to install Service Packets would be enough as well.
>> Maintenance still stands in the Management node in SQL Server 2005. Go to
>> Maintenance Plans and right click on it.
>> Click Maintenance Plan Wizard.
>> --
>> Ekrem Önsoy
>>
>>
>> "Greg Jimson" <nospam@.hotmail.com> wrote in message
>> news:%23rL5E1T7HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> with SQL 2k the maintenance plan wizard proposed defaults for all
>> maintenance tasks. With SQL 2005 this is gone.
>> What are the best practices to setup a "normal" SQL 2005 maintenance?
>> Thanks for any advice
>> Greg
>> --
>> Greg Jimson
>>
>