SSIS on SQL 2005

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RG - 03 Feb 2010 13:34 GMT

Currently, we have a 90gig db which is updated once daily with more than 60
gig worth of data. The update is written in c# and utilizes stored
procedures. There are only a few transactions, but they are enormous, I
guess to maintain integrity of the data.

Is SSIS solid and reliable for the above purpose? Does it provide high
degree of flexibility and reliability? If yes, considering the above case,
is there a reason to think that SSIS will work better than that of c#/stored
procedures system?

Thanks in advance

Reply to this Message

Bob Barrows - 03 Feb 2010 13:43 GMT

> Currently, we have a 90gig db which is updated once daily with more
> than 60 gig worth of data. The update is written in c# and utilizes
[quoted text clipped - 5 lines]
> above case, is there a reason to think that SSIS will work better
> than that of c#/stored procedures system?

I don't know. It depends on what you're doing in those procedures,
doesn't it?
All I can suggest is that you do a simple test: use the data import
wizard in either SSMS or VS to create to create a package to bring in
the data and give it a try.

Signature

HTH,
Bob Barrows

Reply to this Message

Gennadi Gretchkosiy - 08 Feb 2010 04:18 GMT

I believe this is possible and should work better then your C# application.
Just read this article - I hope this helps

http://msdn.microsoft.com/en-us/library/dd537533.aspx

Regards,
Gennadi

PS I know this article for 2008 version, not 2005, but the difference
between them is "pretty minor"
http://www.sql-server-performance.com/articles/biz/SSIS_New_Features_in_SQL_Serv
er_2008_Part1_p1.aspx

> Currently, we have a 90gig db which is updated once daily with more than 60
> gig worth of data. The update is written in c# and utilizes stored
[quoted text clipped - 9 lines]
>
> .

Reply to this Message