"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)"

In SQL Server Management Studio this error appears as:

"Cannot connect to ."

"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)"

From sqlcmd, possible timeout errors include:

"SQL Network Interfaces: Error Locating Server/Instance Specified"

"Sqlcmd: Error: Microsoft SQL Server Native Client : Client unable to establish connection."

"Sqlcmd: Error: Microsoft SQL Server Native Client : Login timeout expired."

"Could not open a connection to SQL Server"

"An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections."

resolution link:
============================
http://msdn.microsoft.com/en-us/library/ms190181.aspx

how many SSIS packages can run in parallel

http://blogs.msdn.com/sqlperf/archive/2008/02/27/etl-world-record.aspx
http://msdn.microsoft.com/en-us/library/dd537533.aspx

best practices for SSIS package performance

http://blogs.msdn.com/michen/archive/2007/04/24/sqlperf-blog-on-ssis-performance.aspx

The performance turning videos here may also be helpful:

http://sqlcat.com/presentations/archive/2009/05/02/designing-and-tuning-for-performance-your-ssis-packages-in-the-enterprise-sql-video-series.aspx

Importing Excel Cell data via SSIS

check this blog

Dougbert.com blog post

(http://dougbert.com/blogs/dougbert/archive/2008/06/18/excel-in-integration-services-part-2-of-3-tables-and-data-types.aspx )

SSIS Packages Running slow

The workaround is to place this entry into the ‘hosts’ file on the Windows Server 2003 machine :

<<<<<
#Fix for slow running SSIS packages
127.0.0.1 crl.microsoft.com


If you're using 2005, this might have something to do with the certificate revocation list.

In 2008 its modified the dtexec configuration to not check the list. The customer could do the same for 2005 by manually editing the file.

See Michael's blog post for more information:

http://blogs.msdn.com/michen/archive/2008/03/14/configuring-net-for-running-ssis-packages-from-custom-applications.aspx

best practices surrounding team development with SSIS

http://blogs.conchango.com/jamiethomson/archive/2007/08/06/SSIS_3A00_-Team-Development-Experiences.aspx

"Exception from HRESULT: 0xC0010014" Foreach Loop Container SSIS

If we create a new Integration Services Project on the servers BI Visual Studio,
chose the Foreach Loop Container,
click edit on it
and click on the three dots on Expressions under Collection we get an error message saying:

"Exception from HRESULT: 0xC0010014".

Resolution:
============================
issue was resolved by registering ‘ForEachFileEnumerator.dll’ using regsvr32.exe:

c:\program files (x86)\microsoft sql server\90\dts\foreachenumerators\ForEachFileEnumerator.dll

As per this link:

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/8cf03f7d-f170-40db-98fa-af151d5b5269