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 |
|
kond.mohan
Posting Yak Master
213 Posts |
 Posted - 2012-06-08 : 06:43:26
|
| Dear allwe have created ssis (ssms 2008 bids )packages source is :oracle destionation is :sql server 2008r2 some of tables are having 6-10 crores of data ------ 2types of packges are created 1) fist one is loading data from source to Destination 2) we have created reports we have stored these reports in ssis packagespackages are scheduled through sql server agent and every moring packges are executed through sql server agent( we have done all necessary indexes creaion and query optimizaion )when ever job is executing i want to improve my package execution and i want to kill the unnecessary process(SUSPENDED,SLEEPING) wihout job fail AND what is the diffference between suspended and sleeping .when ever loading data fro source to destination table locking also happening we have already used in (NOLOCK) clause in every table how to avoid the table locking ----------2)questioin )what is difference between OLDE DB DATASOURCE AND ADO NET DATASOURCE |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2012-06-08 : 06:45:46
|
| You say yoou have already optimised but sounds like that is where the issues lie?Why do you want to kill processes?==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-06-08 : 12:27:19
|
| we have stored these reports in ssis packageshmm..didnt understand that. how do you store report in package? do you mean generate reports using package instead?when ever loading data fro source to destination table locking also happening we have already used in (NOLOCK) clause in every table how to avoid the table locking is there some concurrent loading? are there too many indexes in destination table or any triggers present? if its a bulk load it might be worth dropping indexes before and create them after the data population. you can add them as preceding and suceeding steps in same job itself to ensure correct sequence------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
|
|
|
Package execution(ssms 2008 R2)