March 5, 2010 at 12:10 pm
Have you tried creating a log file?
You mentioned that you went into debug mode, I assume that you set breakpoints?
Double check the properties on your flat file connection manager...
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 5, 2010 at 12:14 pm
I assume that you examined your project in BIDS?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 5, 2010 at 12:28 pm
Are you only having this problem with this query (datasource)?
What happens if you export the results of a small table from one of the sample databases?
What happens if you simplify your query?
When you preview your data that would suggest that something is going on with the flat file connection?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 8, 2010 at 6:47 am
Welsh Corgi (3/5/2010)
Have you tried creating a log file?You mentioned that you went into debug mode, I assume that you set breakpoints?
Double check the properties on your flat file connection manager...
Not entirely sure how to create a log file. The output from the debug has everything succeeding, there are no errors. I'm just not getting the rows output, all I am getting is the header row.
Which properties do I need to check on the flat file connection manager?
-- Kit
March 8, 2010 at 6:50 am
Welsh Corgi (3/5/2010)
Are you only having this problem with this query (datasource)?What happens if you export the results of a small table from one of the sample databases?
What happens if you simplify your query?
When you preview your data that would suggest that something is going on with the flat file connection?
I've had this problem before with queries that span two databases. They run in SSMS just fine, but won't appear through any output. I have to cut and paste from SSMS into a txt file or Excel file to get the file to output.
Not sure how to simplify the query. Thought it was pretty simple to begin with.
Don't see anything specific that would indicate I'd have a problem with the flat file connection. Doesn't mean there isn't something there, I'm having to do a raw data dump and out of the 158k rows, I'm sure there's some junky data in there.
-- Kit
March 8, 2010 at 7:42 am
To create a Log File all you need to do is right click from within BIDS and select Log File.
I would examine the results of the log file.
Also you may need to change your column delimiter or other property because if the delimiter is stored in the Data your Package will bomb.
I would suggest that you consider experimenting with your Package in the BIDS ENvironment.
Also change the source to a query & try pulling in the first record, does it fail?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 8, 2010 at 10:23 am
Welsh Corgi (3/8/2010)
To create a Log File all you need to do is right click from within BIDS and select Log File.I would examine the results of the log file.
Also you may need to change your column delimiter or other property because if the delimiter is stored in the Data your Package will bomb.
I would suggest that you consider experimenting with your Package in the BIDS ENvironment.
Also change the source to a query & try pulling in the first record, does it fail?
I'm using a full version of Visual Studios 2005 so I'm not sure if your advice on BIDS will apply.
I will do a bit more experimentation and let you know the results.
-- Kit
March 9, 2010 at 8:28 am
Okay, found out what the problem was.
It is the "use <database>" as the first line in the query. The Import/Export wizard (and SSIS) don't like that and I got 0 rows because of it. Got rid of that statement and I got the export of the data I needed.
-- Kit
Viewing 8 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply