SQL Server 2005 and 2008 on same machine

  • Hi

    I had installed SQL Server 2005 & 2008 on same machine.

    Following are few things I observed after installation.

    1. I can't see SQL Server Business Intelligence Development Studio

    seprate for 2008 installation. Only I can see SQL Server Business

    Intelligence Development Studio for 2005.

    2. I have SSIS packages developed in both the version.

    I want 2005 developed package should pick up 2005 version of SQL

    Server Business Intelligence Development Studio & 2008 deveopled

    package should pickup 2008 SQL Server Business Intelligence

    Development Studio

    3. How to seprate these installation of different version.

    4. Or Can anyone tell me what are steps to follow if I want want to

    install SQL Server 2005 & 2008 on same machine.

    Thanks

    Saurabh

  • There should be no problem installing both versions side by side.

    Find the .exe files for both versions of BIDS (either in the sql server folders or in the visual studio folders, it depends if you already had visual studio installed)

    For example:

    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" (if visual studio was already installed on your machine)

    Start -> Programs -> Microsoft SQL Server 2005 -> SQL Server Business Intelligence Development Studio. (if only the visual studio shell is installed)

    Create a shortcut to your desktop for both of them. Now you can start the seperate development environments.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Saurabh

    You might consider installing the development tools on a client PC instead of on the server. That way, you can keep your development separate from the function of the server, and leave remote RDP connections to the server available for those who need to do work on the server.

    As for which version of SSIS runs which packages, the only way I've found to be sure of getting the right one is to use CmdExec in your job step instead of the SQL Server Integration Services Package job step type. Specify the full path to the correct DtExec.exe and fill in the parameters - I think you can get them from the SQL Server Integration Services Package type.

    John

  • John Mitchell-245523 (3/31/2011)


    Saurabh

    You might consider installing the development tools on a client PC instead of on the server. That way, you can keep your development separate from the function of the server, and leave remote RDP connections to the server available for those who need to do work on the server.

    As for which version of SSIS runs which packages, the only way I've found to be sure of getting the right one is to use CmdExec in your job step instead of the SQL Server Integration Services Package job step type. Specify the full path to the correct DtExec.exe and fill in the parameters - I think you can get them from the SQL Server Integration Services Package type.

    John

    On a 64-bit server the SQL Server Integrations Services jobstep should always use the 64-bit dtexec, unless the user specifies to use the 32-bit environment by selecting the checkbox for "Use 32-bit environment".

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • True, but I was assuming both versions are 64-bit. Saurabh doesn't specify.

    John

Viewing 5 posts - 1 through 4 (of 4 total)

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