Ms Sql Server Technology Discussions

[Darling999]

[quote name='Kaarthikeya' timestamp='1365435961' post='1303564338']
[b]same thing Dev lo work ainappudu QA lo enduku work avvadu bhayya[/b]?

motham same ey untundi kadaa...I mean atleast the properties of a package will be same kadaa

btw thanks for telling about SIT

DIT ani untadi maa daggara...but adento alochinchali ippudu?
ok...paina naa question ki answer cheppu
[/quote]

same thing antey aren't there any changes in DEV and QA pkgs? nuvvu dev lo changes chestey avi QA lo impact ela avtaayi without migrating them? Props and other stuff nuvvu DEV lo changes chestey QA lo effect avali kada. anduku migrate cehyyamannanu, when both pkgs are same at task and property level then check the Parameter vaules you are are supplying to it.

for Eg: Dev lo C:Test ani ichi QA lo D:Test ilanti chinnc chinnavi eminaa unayemoo check cheyyi. some time we may miss them.

[deals2buy]

nice posts rey loveindia, Littlemoon, DARLING

[Darling999]

[quote name='littlemoon' timestamp='1365436201' post='1303564364']
shrinking database generally prefer cheyadhu anataru... check emi jobs run avhtuanyi .. indexes and log files growth ela undo... .but memu similar issue face chesamu and we did [b]shrink our data and log file sizes[/b]..

n make sure daily data backup run aye tatu so that keeps ur file size growth in place... aina saripovatledhu ante disk space increase cheyali ankunta..
[/quote]

ee point follow avvu, I forgot to say, that works well.

[deals2buy]

[quote name='DARLING...' timestamp='1365436583' post='1303564409']
same thing antey aren't there any changes in DEV and QA pkgs? nuvvu dev lo changes chestey avi QA lo impact ela avtaayi without migrating them? Props and other stuff nuvvu DEV lo changes chestey QA lo effect avali kada. anduku migrate cehyyamannanu, when both pkgs are same at task and property level then check the Parameter vaules you are are supplying to it.

for Eg: Dev lo C:Test ani ichi QA lo D:Test ilanti chinnc chinnavi eminaa unayemoo check cheyyi. some time we may miss them.
[/quote]

ala kaadu bhayya...

ippudu naa daggara PackageA undi Dev lo...andulo nenu kotha changes chesaanu

same PackageA QA lo kuda undi....instead of moving my package from Dev to QA...I made the same changes in QA what I made in Dev..

aa Package Dev lo run avutondi picking up the global variables...but QA lo pick cheskovatledu

[Darling999]

[quote name='Kaarthikeya' timestamp='1365436740' post='1303564435']
ala kaadu bhayya...

ippudu naa daggara PackageA undi Dev lo...andulo nenu kotha changes chesaanu

same PackageA QA lo kuda undi....instead of moving my package from Dev to QA...I made the same changes in QA what I made in Dev..

aa Package Dev lo run avutondi picking up the global variables...but QA lo pick cheskovatledu
[/quote]

Yeah ok by this I can understand one thing. DTS idea ledu Naaku, but check whether you created the variables at package level or task level. adokkati choodu endukantey task level lo variable istey that wont work for other tasks. please check this, I am guessing that might be the reason.

[kumargadu]

[quote name='loveindia' timestamp='1365435924' post='1303564329']

ok nuvvu ye company ki work chestavo konchem PM. same to same issue I got... database size peragatam antey basic ga adhi temp db full avutundi ani... so as far as I can guess, there are jobs running in your databases at a certain time, which are doing the locking and so SQL Server temp db full aipoi, diskspace empty avutundi..

The only thing, and best thing is to find out what job is it and if it is using any sql code in there, try to change it using sql standard procedures. Most of the times, SQL Server lo ee issues LEFT JOINS daggara vastai.. look for those and try to eliminate them if possible..

These are the first steps I would suggest you to do than thinking about shrinking the temp db or what so ever..
[/quote]


we have multiple jobs running every night , any tips on how to find out what job is it ?

[loveindia]

[quote name='kumargadu' timestamp='1365437545' post='1303564538']


we have multiple jobs running every night , any tips on how to find out what job is it ?
[/quote]

trace run cheyyi... one fine saturday / sunday (maintenance window period lo) re run the jobs one by one or see where the locks are when you see the database is full without stopping the services... etc..,

[kumargadu]

[quote name='DARLING...' timestamp='1365436642' post='1303564418']

ee point follow avvu, I forgot to say, that works well.
[/quote]

Thanks bro

[kumargadu]

ok i found it . one of the test database's ldf is 50 GB . f*ck this

[stewiegriffin]

[quote name='kumargadu' timestamp='1365438952' post='1303564693']
ok i found it . one of the test database's ldf is 50 GB . f*ck this
[/quote]
mdf file size entha..
full recovery mode lo unchi, log backups set cheyakapothe, ldf filesize will keep growing..
transaction log backups job setup chey or set the db in simple recovery mode

[littlemoon]

[quote name='kumargadu' timestamp='1365438952' post='1303564693']
ok i found it . one of the test database's ldf is 50 GB . f*ck this
[/quote]

1st shrink that file suppose mdf size 40 gb unte ldf can b like 3gb .. depends on database usage...
in general 2% undali ldf size compared to [size=4]mdf... and auto growth option select cheyali.. [/size]

shrink ayaka daily transaction backup setup cheyandi including previous day trn file delete ayetatu ...

this way file size growth correct untundi and diskspace kuda

[deals2buy]

[quote name='DARLING...' timestamp='1365437200' post='1303564485']

Yeah ok by this I can understand one thing. DTS idea ledu Naaku, but check whether you created the variables at package level or task level. adokkati choodu endukantey task level lo variable istey that wont work for other tasks. please check this, I am guessing that might be the reason.
[/quote]
valid point but earlier when the package was built, Dev lo build chesi QA ki move chesaru...appudu same kind of properties undaali kadaa... can they change on their own?
[quote name='loveindia' timestamp='1365438000' post='1303564595']

trace run cheyyi... one fine saturday / sunday (maintenance window period lo) re run the jobs one by one or see where the locks are when you see the database is full without stopping the services... etc..,
[/quote]
[quote name='littlemoon' timestamp='1365441763' post='1303565035']

1st shrink that file suppose mdf size 40 gb unte ldf can b like 3gb .. depends on database usage...
in general 2% undali ldf size compared to [size=4]mdf... and auto growth option select cheyali.. [/size]

shrink ayaka daily transaction backup setup cheyandi including previous day trn file delete ayetatu ...

this way file size growth correct untundi and diskspace kuda
[/quote] both of u

[kumargadu]

[quote name='littlemoon' timestamp='1365441763' post='1303565035']

1st shrink that file suppose mdf size 40 gb unte ldf can b like 3gb .. depends on database usage...
in general 2% undali ldf size compared to [size=4]mdf... and auto growth option select cheyali.. [/size]

shrink ayaka daily transaction backup setup cheyandi including previous day trn file delete ayetatu ...

this way file size growth correct untundi and diskspace kuda
[/quote]


I did that , Thank you !!!

[loveindia]

[quote name='kumargadu' timestamp='1365438952' post='1303564693']
ok i found it . one of the test database's ldf is 50 GB . f*ck this
[/quote]

ldf file size ekkuva untey just shrink it man... thats it.. very easy steps.. no problem will come by doing that... temp db ni maatram eppudu shrink cheyyoddu...

[deals2buy]

[quote name='loveindia' timestamp='1365445893' post='1303565489']

ldf file size ekkuva untey just shrink it man... thats it.. very easy steps.. no problem will come by doing that... temp db ni maatram eppudu shrink cheyyoddu...
[/quote]

cheste em prob avutundi? okasari nenu indexes pettakunda/petto gurthu ledu kaani oka data load run chesa....oka 30 min ayye sariki DBA gaadu em chestunnav desk daggara...disk space ala aipoindi okkasare annadu