Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ava_mina
Starting Member
3 Posts |
 Posted - 2008-10-22 : 08:56:38
|
| We use SSIS 2005 in our project to load large size data (about 180 K records) into our database (including validation, cleansing and other operations)...Sometimes we receive the following error that shows a failure in TCP/IP connection to the database, while failing to complete the SSIS package execution:"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"kindly note the following:- The problem is unpredictable for the same scenario, i.e. for the same loading file, sometimes it happens and sometimes not!- This problem may not arrise during the same SSIS component each time!- We checked our network and connection resources and seams fine!I don't know whether this relates to SSIS or generally happens in our database, but it does happen during SSIS package execution...Any help? |
|
|
ava_mina
Starting Member
3 Posts |
Posted - 2008-10-23 : 06:11:53
|
| I wish to add that this error happened again when dealing with large size data within out .NET application (away from SSIS) |
 |
|
|
rgombina
Constraint Violating Yak Guru
319 Posts |
Posted - 2008-10-23 : 07:13:04
|
quote:
Originally posted by ava_mina
I wish to add that this error happened again when dealing with large size data within out .NET application (away from SSIS)
How is .NET application processing data that creates the error? Is the application doing the validation, cleaning and doing other data manipulations too? |
|
|
|
ava_mina
Starting Member
3 Posts |
Posted - 2008-10-23 : 18:59:46
|
| Hi rgombina,Thanks for your quick reply...We use our .NET web application to call SSIS package that performs large data size validation, cleaning and then loading into our database. Again the .NET web application calls special stored procedures after loading to calculate some KPIs (Key Performance Indicators) for the loaded data... So, we noticed that the mentioned error mostly arrises during the SSIS execution, while sometimes arrises during the KPI Calculation procedures, which leads us to think that this error does not relate particulary to SSIS, but it seams happening when processing large data!We tried much to search on this error in other forums, but still we find general causes that are not applicable on our scenarios... |
|
|
|
rgombina
Constraint Violating Yak Guru
319 Posts |
Posted - 2008-10-24 : 07:28:26
|
| No problem. Okay, so .NET is just an app executing SSIS.Question - just curious, 180K records is not much but it could create/cause timeout depending on your data flow design (not saying bad because I don't know). Mind asking how and what tasks are you using to acomplish the processing (ex SQL Task, Script Task, Script Component, etc)?For all we know too it could be network connection or SQL log full but as you mention it is all okay. Just trying to see big picture here. |
|
|
|
igorblackbelt
Constraint Violating Yak Guru
407 Posts |
Posted - 2008-10-24 : 09:31:18
|
| Maybe you have a limited network, for instance, I used to work in a place 2 year back where they were in a 10mbps network and that caused a lot of issues on data intense processes.You may already have this in place, but if you don't, try setting the numbers of rows per batch on your destination connection, try limiting it to 10K rows and let us know if that does the trick.---http://www.ssisdude.blogspot.com/ |
|
|
|
|
|
|
|
|
TCP/IP Provider Error When Loading Large Data