October 11, 2013 at 1:19 am
Hi Team,
My SSIS package is very slow only for past 2 weeks. Before it used to run in 2 hrs now it is running in 8 hrs. Today the package completely failed with error ": Could not allocate a new page for database 'Test' because of insufficient disk space in filegroup 'PRIMARY' ". Can PRIMARY memory allocation be a reason for the package becoming slow?
Need your opinion to know if I increase the PRIMARY memory space will this issue will be resolved. Most importantly I would like to know will it be a permanent fix.
Please suggest what are the parameters I should consider in the SSIS package and in the source(Oracle) and destination(MS SQL server) to give a permanent fix.
Oracle is 9i and SQL server 2008R2. Data pull is from 5 tables each with 300,000 rows and 10 columns.
Thanks
Jim
October 11, 2013 at 1:31 am
2 hours for 5 times 300.000 rows is slow. (ok, 8 hours is even slower)
What are you doing inside the package?
Regarding the error: PRIMARY filegroup has nothing to do with memory. The filegroup is where your database pages are saved unto disk. Your destination database has run out of size. Either there's a maximum size defined for the database, or you've run out of disk space.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 11, 2013 at 3:18 am
Also try attunity connector for oracle source.
Pramod
SQL Server DBA | MCSE SQL Server 2012/2014
in.linkedin.com/in/pramodsingla/
http://pramodsingla.wordpress.com/
October 11, 2013 at 4:23 am
Thanks Koen. So if I increase the destination database size or the disk space, the package load performance can be improved? I'm asking this because if increasing the size will help the performance, I have to contact my DBAs to do the same.
Please suggest.
October 11, 2013 at 4:53 am
Jim1234 (10/11/2013)
Thanks Koen. So if I increase the destination database size or the disk space, the package load performance can be improved? I'm asking this because if increasing the size will help the performance, I have to contact my DBAs to do the same.
Not necessarily.
Enlarging the size of the database file will stop your package from failing.
However, if the database file size is always a bit too small and it has to autogrow each time (I don't know what the settings are on the database) and the autogrow settings are inadequate, it is possible that the database file is more busy with trying to grow than storing data. So yes, choosing a decent size for the database file might improve performance, but not necessarily.
You need to test what the bottleneck of your package is. Is it the source, the destination or something in between?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 11, 2013 at 5:50 am
Thanks again Koen!! The package is a loading data from oracle to SQL server from 5 tables with each table of 200,000 size approx. Using Oledb providers. The 5 queries are in 5 Data Flow which are executing parallel. This used to take around 2 to 3 hrs and now it is taking around 8hrs.
Your suggestion on what are the parameters I should check will greatly help!!
Attunity we are not able to use as of now, but will plan in future..
October 18, 2013 at 12:52 am
Thanks! The problem is solved by increasing the space...
October 18, 2013 at 1:10 am
Jim1234 (10/18/2013)
Thanks! The problem is solved by increasing the space...
Great, glad you got it solved.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply