.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

SSIS 2005 & 2008 BIDS and VS2005/2008 Will VS2010 work with either SSIS package?

Posted By:      Posted Date: September 13, 2010    Points: 0   Category :Sql Server
I've read the old posts about having to have the BIDS version match the SSIS package version. My question is with VS2010 is there any change? Can I edit either of the old versions of SSIS packages in VS2010 or do I have to have 3 versions of Visual Studio/BIDS on my machine? TIA J

View Complete Post

More Related Resource Links

Diffrences in SSIS 2005 and SSIS 2008?

Hi All,   How to convince interviewer in  major differences in ssis 2005 and ssis 2008.In my system I have ssis 2008.Can I install ssis 2005? How to install? Thanks CMK…

How to create a SSIS package to import records form SQl Server 2008 tables to text files

I am a newbie to SSIS and would like to create a package to accomplish the task referenced in the above title. Will appreciate any links and pointers in the right direction.   Thanksakoranteng

SSIS 2008 - Excel Source using SQL Connection cancels as soon as package runs.

Let me preface this by saying I'm brand-new to SSIS development. I'm using 64-bit SSIS 2008 and I'm trying to read an Excel spreadsheet using OLE DB. I've already run into and corrected the Run64BitRuntime problem.  Now when I invoke the Package it cancels immediately with the following output: SSIS package "Lesson1X.dtsx" starting. Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning. SSIS package "Lesson1X.dtsx" finished: Canceled. The program '[5400] Lesson1X.dtsx: DTS' has exited with code 0 (0x0). When I edit the Excel Source component itself there are no errors and I am able to Preview the results successfully.  If I use Table or View to access the file, the package runs successfully. Any suggestions will be greatly appreciated. Thanks

SSIS Package / SQL Agent Job never ends on SQL 2008 R2



I have run into a strange problem and hoping someone may have a suggestion.

We have a set of SSIS packages that are developed in BIDS 2005. The packages are all executed by SQL Agent Jobs on a scheduled basis. These packages have been running on numerous SQL 2005 instances for the last year or so with no issues being experienced.

We recently has our first customer start running SQL 2008 R2 and we have internally upgraded to SQL 2008 R2 in our development environment. We are not converting the packages to SQL 2008 as we still need to support customers who are running SQL 2005. The problem is that in both our dev environment and at this particular customer, we have seem a random issue where the SQL Agent job never seems to end. Most of our jobs normally execute in less than 2 minutes, but occasionally (one or twice a week) a random job will just not end until we manually cancel it. We don't know if it is the SSIS package that is not ending or the SQL job.

We never experienced this on SQL 2005.

Anyone have any ideas what may be causing this? Any suggestions for troubleshooting?

Any help will be much appreciated


Craig Bryden - Please mark correct answers

Copy SSIS packages from 2005 to 2008

I have both vs 2005 and vs2008 on the same pc. When i try to copy the package from the BIDS 2008 from file Copy as i get an error

 Storing or modifying packages in SQL Server requires the SSIS runtime and database to be the same version. Storing packages in earlier versions is not supported.

Do you know how to fix this issue.

SQL Agent - Running SSIS Package - Windows Server 2008/Windows 7 - Messenger Services


We have tried to run a SQL job for SSIS Package. But it failed during the execution with the error "[364] The Messenger service has not been started - NetSend notifications will not be sent". But in the job, no notifications have been configured and in windows server 2008/Windows-7 there is no messenger service at all.

When we search for the the messenger service in windows 7/windows server 2008, we found that service is not in both the OS and it was replaced by msg.exe. 

Any help or workaround would be appreciated.

Thanks in advance.

PS: The normal SQL jobs other than SSIS are working fine without any error.

Vijay Pandurangan

SSIS on Cluster also 2005 packages and 2008 db connections and jobs?


Hi, multipart questions.

We have a SQL 2008 Cluster where we do not want to install SSIS.  We have a SQL 2005 SSIS instance on another server  for packages.

here goes

1. Can we configure jobs on the SQL 2008 custer to point to the 2005 SSIS instance? and do we need SSIS installed on the SQL 2008 cluster to do this?

2. Can we run jobs on a SQL 2005 instance, pointing to a SQL 2005 SSIS instance/packages on a third server that connect to a SQL 2008 DB instance . I know that sounds crazy, but where exactly is the CPU and memory load in that design.. job on one server, package a seperate server and db on a third server.?

3. As mentioned, I have SQL 2005 SSIS instance.  I have local admin on that server and can connect to the ssis instance from my sql 2005 sql client on my desktop.  I added a new user to the server and added them to the SSIS and users group. I also made sure they could write to the folder where they will deploy packages. However, they get some kind of access denied while trying to connect, unless I give them local admin on the server.  What more access do they need than to be in the users and SSIS group and have write access to an SSIS deployment folders?


Many Thanks.

How to open the SSIS packge in 2005 which opened in 2008


Hi I have a package which was done in SSIS 2005 and I have opened that in SSIS 2008. I want to open this back in 2005 but its throwing an error. How to Open this package back in 2005.

The error message: Error 1 Error loading Package.dtsx: The version number in the package is not valid. The version number cannot be greater than current version number.  C:Processing\Operational Packages\Package.dtsx1 1 

Visual Studio 2008 and SQL Server 2005 SSIS packages


My home machine has sql 2005  and Visual Studio 2005 installed. I uninstalled VS 2005 (RTM) and installed VS 2008 (RTM) in its place. I then found that the SSIS templates were missing. Lesson: don't uninstall VS 2005 if you want to use SSIS 2005!


1. Is there any "workaround" to this issue?


2. (If the answer to 1 is "No") I will install VS 2008 side-by-side with VS 2005 on the same box.  When the SSIS issue is finally resolved, can I uninstall VS 2005 without doing damage to the VS 2008 install?










Executing SSIS 2008 in SQL 2005


I've created a SSIS package in SQL 2008. I tried running the package in SQL 2005 but was prompted with the error below.


"The version number in the package is not valid. The version number cannot be greater than current version number."

"Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number."


Is there any method that I could use to enable the package to be executed in SQL 2005?

SSIS 2005-2008 web service task limits



I'm finding some articles or white papers about the limits or incompatibilities of SSIS 2005-2008 web service task.

Any suggests to me, please? Many thanks

Schedule problem with SSIS package on SQL Server 2008

Hello there

Step 1 - I created my first SSIS package (simple ole db source to file destination scenario) in BIDS 2008. I created and run this on the SQL Server 2008 - SP1(on Win2k3 SP2 - 64 bit machine). This integratin scenario creates a flat file with some records in it (records modified today). This packages runs ok from BIDS.

Step 2- After deploying this SSIS package to the SQL Server 2008, I was able to run it successfully. The package created a flat file with some records.

On the two occasions above, the ssis package did exactly what I wanted it to do.

I tried to create SQL Server Agent job selected the Type as SSIS package, allowed this package to run under Windows Authentication (service account - same account used as in Steps 1 & 2). Before scheduling, I thought why not run this manually. The job ran successfully (looked at the success message and the history of the job), but a flat file was created (as expected) without any records (not as expected!)

Please note I have tried the default protection level ("EncryptSensitiveWithUserKey") as well as ("DontSaveSensitive") on the package.

I am suspecting that when the SSIS package is scheduled the SQL Server Agent is unable to pass the authentication to the SSIS package !?

Some help will be appreciated.


Merge Join in SSIS 2005 Vs 2008



I have a process which reads from 2 tables (using two connection managers) and "merge join" them to a third table by using left outer join.

This process is implemented on SSIS 2005 and SSIS 2008 identically, however, for some reason I get less records at the third table at the 2008 process.

When implementing this merge join on Sql Server 2008 and Sql Server 2005 I get the same result as I got at the SSIS 2005 process - so it seems like the problem is at the SSIS 2008 process.
I've checked the merge join properties - they look similar on 2005 and 2008.
Does anyone knows if the 2008 merge join object should be configured differently than the 2005 merge join?
I have nulls on some the fields that connect the two tables - do you think it's got to do with it?
What else can I check?

SSIS package runs very slow on SQL 2008 R2 server, runs very quickly on virtual XP machine


Hi All,

I've been troubleshooting this issue on and off for a few weeks now.  I've scoured these forums and looked through sqlis.com, but I'm just about out of ideas.  Here's what's happening.

I have a *very* simple integration services package I developed on a  virtual Windows XP machine running on my workstation.  The package uses a script task to simulate a one-row source with four columns (int, char(64), varchar(512) and char(2)) and then passes that off to a fuzzy lookup.  The fuzzy lookup is running against a table of only about 6,000 rows.  The package then inserts the results into a table and exits.

When I run this from my virtual XP machine, it completes in 1-2 seconds.

When I execute this on the server (either as a job or through DTExec) it takes 14-18 seconds.  The server stores the package in MSDB and is also the location where the fuzzy lookup happens.

I've tried using the 32-bit runtime, creating 32- and 64-bit aliases to the server, changing the name of the server from the name to the IP address and port, stopping/restarting SQL Agent and SSIS Services... none of this seems to change the execution time.

The one thing I've found is that if I enable package logging on the logging tab of the job, using the SSIS Log Provider for SQL Server and pointing it to the same connection st

SSIS 2008 Package with OLE DB provider MSDAORA.1 does not pass validation


Hello there---

I have run into a problem that apparently others have hit, too, but I don't seem to see any definitive solutions to the problem... I have created a package in BIDS (VS2008) for SQL 2008, living on a Windows Server 2008 R2 box (64-bit OS). I have set up my connections to an Oracle DB and my local SQL Server via Connection Managers, and testing the connections rolls successfully. My Data Flow tab is all set with the source db (Oracle) and my destination db (SQL 2008) as well as a Data Conversion step in between. But when I run the package from within the BIDS (F5), the package does not pass validation. I am getting the following messages...

[Connection manager "OTAP.rmarkarian"] Error: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider MSDAORA.1 is not registered -- perhaps no 64-bit provider is available.  Error code: 0x00000000.
An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".

I have looked at the following thread in this forum (http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/920a0817-d9

Using Conditional Split data Transfer in SSIS 2008

This article uses the Integration Services Conditional Split Data Transformation element to filter and transfer data from a set of flat text files to SQL Server database table. The concept can be easily extended to apply to any other source or destination such as Microsoft Excel. This scenario is useful in creating denormalized database tables in a reporting and analysis situation.

Convert 2005 RDLC to 2008 using VS2010


Hi and thanks.


I'm getting an error on serveral reports that I built  in VWD2005 (express) using the reportviewer control.  Trying to edit the rdlc file in VS2010, VS2010 asks if i want to convert the file to RDLC 2008 format and I click ok.  When I build the site, I get this error (and of course also when the report is ran):


Error 1 The report definition is not valid.  Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition' which cannot be upgraded. C:\inetpub\wwwroot\mastercardlcm\Reports\WorkLists\OpenSRStatus.rdlc 1 


Here is my web.config concerning the RDLC assemblies, etc.

			<add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
		<compilation debug="true">
				<add assembly="Microsoft.ReportViewer.WebForms, Version=, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
				<add assembly="Microsof
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend