Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6007801
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T01:44:03+00:00 2026-05-23T01:44:03+00:00

We are using SSIS with SQL Sever 2005 / VS 2008. My colleague insists

  • 0

We are using SSIS with SQL Sever 2005 / VS 2008.

My colleague insists that we cannot use a scripting component inside the SSIS package because this will introduce executable code into the process then the CLR will have to be installed on the database server that is executing the job. Installing anything (if it doesn’t exist already) on production machines would be problematic.

My question is, does adding the scripting component to a SSIS package cause it to have to call the CLR whereas SSIS did not have this dependency before?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T01:44:04+00:00Added an answer on May 23, 2026 at 1:44 am

    Please refer the following MSDN link.

    Hardware and Software Requirements for Installing SQL Server 2005

    As per the documentation, SQL Server 2005 installs .NET Framework 2.0 on the machine (except for the Express edition, which requires manual install). SSIS packages require SSIS runtime engine. If you have that SSIS component installed, you don’t need to install any other component to execute the packages even if they use Script Task or Script Component.

    Following is the direct quote from MSDN and screenshot #1 highlights the section in the MSDN.

    Quote from the MSDN:

    SQL Server Setup installs the following software components required by the
    product:
     - Microsoft .NET Framework 2.0
     - Microsoft SQL Server Native Client
     - Microsoft SQL Server Setup support files
    

    Hope that helps.

    Screenshot #1:

    1

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.