Post reply

Post Installation

  • April 2, 2009 at 6:41 am

    #198751

    Hi,

    Ia m new to SQL server, its been 6 months or so. Trying to get some knowledge. Hope you guys understand and help me out to the questions I ask please 🙂

    I am just wondering, What are the post installation steps that you should consider after installing SQL server on a production?

    and also

    Applying service packs and hot fixes, what steps do you have to take on a current production system? For example if you have to install a new service level pack or a hotfix how do you go about it?

    It's not an interview question or anything like that:-D

    Thanks a lot

  • April 2, 2009 at 6:49 am

    #970605

    Achtang (4/2/2009)

    Hi,

    Ia m new to SQL server, its been 6 months or so. Trying to get some knowledge. Hope you guys understand and help me out to the questions I ask please 🙂

    I am just wondering, What are the post installation steps that you should consider after installing SQL server on a production?

    go into sql server configuration manager and configure any options within there, also create/implemement backup and maintenance regimes

    Achtang (4/2/2009)

    and also

    Applying service packs and hot fixes, what steps do you have to take on a current production system? For example if you have to install a new service level pack or a hotfix how do you go about it?

    It's not an interview question or anything like that:-D

    Thanks a lot

    backup all your databases first before applying any SP's or hotfixes would be sensible. There is no rollback from SP's or hotfixes but you could

    backup all user and system databases

    take a ghost image of the server

    install SP/hotfix

    but the downtime required in Live may not be possible and if you decide at some point after it hasn't worked rolling back would lose data. Implement these on a test bed first before applying to Production (Virtual Server 2005 is great for this).

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • April 2, 2009 at 7:00 am

    #970621

    Thanks for your kid reply Perry.

    go into sql server configuration manager and configure any options within there, also create/implemement backup and maintenance regimes

    Did you mean the security configuration I meant the required port?

    and also

    Did you mean to design our maintenance plans and backup plans?

    There is no rollback form SP's or hotfixes but you could

    this one you meant if we apply SP3 we cannot apply SP2 again? and also you have to take the server offline isn't it? which means do you have to start the server in single user mode? and then perform hotfixes?

    take a ghost image of the server

    I dint get this really.

    Please be patience I want to know a lot from the real time perspective, I know you can go through books and articles but I want it in the real world, I am not getting a chance to do all this as still I am at junior level and you know my senior doesnt want me to go there...

  • April 2, 2009 at 7:12 am

    #970638

    Achtang (4/2/2009)

    Did you mean the security configuration I meant the required port?

    and also

    Did you mean to design our maintenance plans and backup plans?

    for sql2005 post installation you should ideally open "SQL server configuration manager" and set any port, service or protocol options (such as sql instance static port number) and also open "surface area configuration" and configure any options within there (e.g. allowing remote connections or disabling xp_cmdshell, etc)

    Achtang (4/2/2009)

    this one you meant if we apply SP3 we cannot apply SP2 again? and also you have to take the server offline isn't it? which means do you have to start the server in single user mode? and then perform hotfixes?

    no, if you install SP3 you cannot un install it.

    If you install SP3 then SP2 is redundant anyway

    Ghost is a clone software from Symantec and can image machines for replication and backup or restore scenarios. Realistically though you just wouldnt do that in Production, you would use a testbed environment to ensure the SP's or hotfixes dont cause you any problems then apply to Production

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • April 2, 2009 at 7:25 am

    #970652

    ok! Great I have some idea:

    You should always test it in the test environment before installing it on the production. And then should you test the applications as well that connect to the real production system after SP level installation?

    and also on SAC you should set the protocols for the SQL Server, default is 1433 but how to change that if we want to? or does SQL server chose it by default while installing?

    allowing remote connections

    This one which means if someone off the site wants to connect to our sql server using their installed SSMS? is it?

    no, if you install SP3 you cannot un install it.

    Danger!!! so you should always test it. Good one!

    What is the dfference between service packs and hotfixes? are they both the same? If not, would you follow the same procedure to install both?

    Thanks again :=)

  • April 2, 2009 at 7:50 am

    #970690

    You should review the Security Best Practices paper from Microsoft. This will give you a good head start.

    http://download.microsoft.com/download/8/5/e/85eea4fa-b3bb-4426-97d0-7f7151b2011c/SQL2005SecBestPract.doc

  • April 2, 2009 at 7:56 am

    #970704

    Achtang (4/2/2009)

    What is the dfference between service packs and hotfixes?

    a hotfix addresses a single issue. A service pack is a roll up of many independant hotfixes, etc

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • April 2, 2009 at 7:58 am

    #970707

    Perry Whittle (4/2/2009)

    Achtang (4/2/2009)

    What is the dfference between service packs and hotfixes?

    a hotfix addresses a single issue. A service pack is a roll up of many independant hotfixes, etc

    Oh ok! so when you apply a hotfix to the production server do you have to follow the same procedure as you install SP's?

    Thanks a lot 🙂

  • April 2, 2009 at 8:00 am

    #970708

    SA (4/2/2009)

    You should review the Security Best Practices paper from Microsoft. This will give you a good head start.

    http://download.microsoft.com/download/8/5/e/85eea4fa-b3bb-4426-97d0-7f7151b2011c/SQL2005SecBestPract.doc%5B/quote%5D

    Great SA thanks for that. I am going to go through that. So, you think i should follow the practices mentioned in the document?

  • April 2, 2009 at 8:13 am

    #970726

    I would look at each of these recommendations closely and see which ones best fit your environment. Like with everything else, never a one solution fits all.

  • April 2, 2009 at 9:47 am

    #970849

    ok! Anybody know what is a SQL Best practice analyzer? Is it run against the servers duriong production? Or before going into production?

  • April 2, 2009 at 9:49 am

    #970853

    and also how do you apply hotfixes? I mean do you have to install it the same way as a SQL Server service pack? I mean do you have to take the same steps as you would for a SP install?

  • April 2, 2009 at 9:50 am

    #970857

    Achtang (4/2/2009)

    and also how do you apply hotfixes? I mean do you have to install it the same way as a SQL Server service pack? I mean do you have to take the same steps as you would for a SP install?

    generally, yes

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • April 2, 2009 at 10:00 am

    #970870

    Best practices analyzer is usually run when you're ready to go to Production. That will be your baseline.

    Once you, are in Production, you would need to run it to ensure there have been no changes to the configurations. I usually run it post an application install where the app requires elevated privileges on the database to install. Just another sanity check to ensure no unnecessary changes were made to the environment.

    I would use this tool as a starting point and as you get more acquainted with SQL Server you could then write your own health checks or use a third party tool for this as well.

  • April 2, 2009 at 10:13 am

    #970887

    Perry Whittle (4/2/2009)

    Achtang (4/2/2009)

    and also how do you apply hotfixes? I mean do you have to install it the same way as a SQL Server service pack? I mean do you have to take the same steps as you would for a SP install?

    generally, yes

    Thanks again !!

    ok! So hotfixes are release by MS frequently than SP's, so would you install them as you need or is it guarantee that you would have to install it because of some security glitches?

    So, basically all the users have to get disconnected from the servers- so do you perform it a business hours or would you perform it at off business hours?

    Or may be if you have a DR server you direct the applications to the DR server may be isn't it?

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply