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 6897943
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T07:14:00+00:00 2026-05-27T07:14:00+00:00

I have a Visual Studio 2005 BIDS project that exports about 30 database tables

  • 0

I have a Visual Studio 2005 BIDS project that exports about 30 database tables from one system database, to another database.

Occasionally I need to add a table to my exportation process. Also, since the genesis of the SSIS Package project, I’ve had to update it maybe 8-12 times. Each time I haven’t had any troubles with the Visual Studio Designer or loading the project.

Today I needed to add another table to the exportation project but there is a problem. When I open Visual Studio 2005 and open the project, the designer window tries to open my package.dtsx file but VS just hangs and never actually loads the file to the designer. If I try to interact with the VS window, a ballon pops up from the Windows task pain stating that “Microsoft Visual Studio is Busy.”

My package and my VS project has been working fine since my last deployment to the SQL Server. This is a new issue, and I’ve never seen it before.

Is there a way that I can modify my Visual Studio solution file(s) so that my Package.dtsx file doesn’t automatically load into the designer?

Alternatively, is there some method, procedure, utility, etc. that I can use that may be able to clean up my Visual Studio Solution or Project?

Ultimately I need to solve the problem with my Package file, but I know that can be a bit of a vague problem with such limited information. For now, I’d prefer to be able to open up my Visual Studio solution without having my file automatically load into the designer.

  • 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-27T07:14:00+00:00Added an answer on May 27, 2026 at 7:14 am

    Based on your comment, delete or move the .suo file. That is the file that contains all your opened files in your project solution.

    By default, the DelayValidation property on the Control Flow Tasks are set to False. That means every time, you open a package, all the connection managers will be validated to make sure that they are still valid.

    If I am dealing with a large package, I usually prefer to set the DelayValidation property at least on the DataFlow tasks to True so that the validation of the connection managers used inside the DataFlow task happen only during package execution and not every time I open it.

    Read more about the DelayValidation property in the following MSDN link.

    DtsContainer.DelayValidation Property

    Coming back to your problem, make sure that no packages are open when you close the solution. That way when the solution is opened next time, it won’t try to load any package in IDE.

    If that doesn’t work, right-click on the SSIS project and select Properties. Make sure in the Debugging section, the StartObjectID property is not set to any particular package in the solution. Below screenshot was taken from SSIS 2008 R2 that VS 2008 Shell.

    Hope that is what you are looking for.

    Properties

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

Sidebar

Related Questions

I am using C++ and Visual Studio 2005. I have a project that memory
I have a visual studio 2005 project with a custom build step that copies
I have a Visual Studio 2005 C++ program that runs differently in Release mode
We have a large Visual Studio 2005 C++/Mfc solution, 1 project with around 1300
Microsoft Visual Studio (2005 and 2008) seems to have fun shuffling the Project IDs
The installer insist that I have Visual Studio 2005 installed. This brings me to
I have a Visual Studio 2005 C++ project, it is a console application. I
I have two Visual Studio 2005 solutions, one of which builds a binary and
I have Visual Studio 2005 (BIDS) set to Check out automatically when a file
I have a solution with two project in Visual Studio 2005. I want to

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.