Jump to content

SQL Question Requested!!!


Recommended Posts

Posted

[quote author=meghana9 link=topic=164798.msg1980014#msg1980014 date=1299607430]
instead of selecting table ..select 'sql command' in that

i think you can try this query inorder to lock that table

SET TRANSACTION ISOLATION LEVEL READ COMMITED
GO
BEGIN TRANSACTION
SELECT * FROM TABLE
COMMIT TRANSACTION

idhi source select chese apudu.. sql command lo use chesthe work avuthundemo  sCo_hmmthink sCo_hmmthink
[/quote]

Ya nenu inko SQl command use cehstunna locking and aunlocking but adi Data flow task(DFT) painaa oka sql LOck cheyyataaniki and DFT kindha oka sql Lock open cehyyataaniki. But naa doubt enti antey if madhyalo SSIS package fail ayitey. Bhajana modalavtundi Production loo. So edainaa ans untey Elp Flzzzz.

Posted

I donno..whether dis could help u r not......

n the SSIS designer, in the Data Flow task, edit the Destination component. There's a [b]Table Lock checkbox[/b]. It is probably checked, which tells the process to lock the table until the data load is complete.

You have a couple of options to address this. First, is it important that one SSIS package must complete loading data before another one can start? If the answer is No, then you can uncheck the Table Lock option in the Destination component. This will allow SQL Server to manage the simultaneous data loads.

If you must let one package complete before other packages can run, then you may want to create an SSIS task that checks to see if the table is available for loading. If the table is being loaded, then stop the SSIS package and recheck later. You could even handle this in your console app.

Posted

[quote author=Ranga_The_Donga link=topic=164798.msg1980338#msg1980338 date=1299610748]
I donno..whether dis could help u r not......

n the SSIS designer, in the Data Flow task, edit the Destination component. There's a [b]Table Lock checkbox[/b]. It is probably checked, which tells the process to lock the table until the data load is complete.

You have a couple of options to address this. First, is it important that one SSIS package must complete loading data before another one can start? If the answer is No, then you can uncheck the Table Lock option in the Destination component. This will allow SQL Server to manage the simultaneous data loads.

If you must let one package complete before other packages can run, then you may want to create an SSIS task that checks to see if the table is available for loading. If the table is being loaded, then stop the SSIS package and recheck later. You could even handle this in your console app.
[/quote]yup ante destination task lo table lock cheste saripoyidi...ayipoyidi oksari load ayyaka automatic ga unlock ayyidi....

Posted

[quote author=nenuVedava link=topic=164798.msg1980298#msg1980298 date=1299610385]
Ya nenu inko SQl command use cehstunna locking and aunlocking but adi Data flow task(DFT) painaa oka sql LOck cheyyataaniki and DFT kindha oka sql Lock open cehyyataaniki. But naa doubt enti antey if madhyalo SSIS package fail ayitey. Bhajana modalavtundi Production loo. So edainaa ans untey Elp Flzzzz.
[/quote]mi issue solve ayindha??  sCo_hmmthink sCo_hmmthink
ela chesaro ikada post cheyandi.. so that someone like me can learn  sSa_j@il sSa_j@il

×
×
  • Create New...