Ms Sql Server Technology Discussions

[littlemoon]

[quote name='Kaarthikeya' timestamp='1365433674' post='1303564071']
nenu Dev lo DTS package ki konni global variables setup chesaa

When I save the package and then open it with QA environment, does those global variables work?

If so, Dev lo save chese mundu set chesina values ey load avutaya leka kotha values dynamic ga load avutaya QA lo?
[/quote]

specific to that environment untundi changes.. as far as I know QA lo a DTS package malli copy cheyali anktuntaa.. (I am not sure ) [size=4] [/size]

[deals2buy]

[quote name='littlemoon' timestamp='1365434314' post='1303564143']

specific to that environment untundi changes.. as far as I know QA lo a DTS package malli copy cheyali anktuntaa.. (I am not sure )
[/quote]

ardham kaale

so instead of moving package from Dev to QA, QA lo package ni changes cheyyali ani telling aa?

[Darling999]

[quote name='loveindia' timestamp='1365390830' post='1303561945']

classes start chesanu... 8 members unnaru... nuvvu and chelsea join avta antey ok.... kaani konchem mee employer ni adigi oka 250 donate cheyu, dat is actually to build a computer for our sql needs only.. no lite antey u can join free.. let me know, add chestaa... neeku chelsea telistey tanaki kuda cheppu naaku pm pettamani..
[/quote]

ididgondi masteru, nannu kudaa join cheskondi, SQL nerchukovaali nenu kudaa.. pm me details please.

[Darling999]

[quote name='Kaarthikeya' timestamp='1365434423' post='1303564157']
ardham kaale

so instead of moving package from Dev to QA, QA lo package ni changes cheyyali ani telling aa?
[/quote]
nuvvu package level lo variables set chestey, vaatini ey environ ment lo ayina use cheyyachu. No matter Prod or Dev or SIT. varaiables remain same there.

eg: Dev lo oka package ki pkgname aney variable create cehsi andulo SSIS ani name ichi save cehskunnav anukoo. danni QA ki migrate cehsi akkada testing chestey. variable and its value reamins Same. No change would occur.

[Darling999]

[quote name='littlemoon' timestamp='1365434314' post='1303564143']

specific to that environment untundi changes.. as far as I know QA lo a DTS package malli copy cheyali anktuntaa.. (I am not sure )
[/quote]

Packages pakka copy cheyyali, but changes wont be specific.

just fyi

[deals2buy]

[quote name='DARLING...' timestamp='1365434828' post='1303564192']
nuvvu package level lo variables set chestey, vaatini ey environ ment lo ayina use cheyyachu. No matter Prod or Dev or SIT. varaiables remain same there.

eg: Dev lo oka package ki pkgname aney variable create cehsi andulo SSIS ani name ichi save cehskunnav anukoo. danni QA ki migrate cehsi akkada testing chestey. variable and its value reamins Same. No change would occur.
[/quote]

DTS lo Set Global variables ani oka option untundi kada bhayya

akkada nenu munde anni values ichaanu....ala ichi package run chestunte its not picking up the variables in QA

but same thing Dev lo chesinappudu it worked for me....

FYI, I didn't migrate the package from Dev to QA. I've made changes directly in QA same as Dev...

Do you think that matters really?


btw SIT ante endi?

[littlemoon]

[quote name='DARLING...' timestamp='1365434881' post='1303564199']

Packages pakka copy cheyyali, but changes wont be specific.

just fyi
[/quote]
Thanks.. I was not sure about changes...

[Darling999]

[quote name='Kaarthikeya' timestamp='1365435086' post='1303564223']
DTS lo Set Global variables ani oka option untundi kada bhayya

akkada nenu munde anni values ichaanu....ala ichi package run chestunte its not picking up the variables in QA

but same thing Dev lo chesinappudu it worked for me....

FYI, I didn't migrate the package from Dev to QA. I've made changes directly in QA same as Dev...

Do you think that matters really?


btw SIT ante endi?
[/quote]
Ya adi matter avtadi kada mari, akkada packages ikkada packages same undaali, for safer options we migrate the latest to test environment, so that no changes are skipped.

SIT antey system integration testing, idi oka environment nundi inko environment ki code movement or package movement appudu avi teeskuni changes apply avtunnayoo levoo check chestaam. just like rough notes.

[Darling999]

[quote name='littlemoon' timestamp='1365435101' post='1303564224']
Thanks.. I was not sure about changes...
[/quote]
NP. tc

[kumargadu]

bros,
ma database size roju roju ki perigipootundi almost disk full aiepooindi , online check chesthey shrink is not a good option ani undi , Are there any other ways to reduce the size or do we have to add extra disk space?

[loveindia]

[quote name='Kaarthikeya' timestamp='1365435086' post='1303564223']
DTS lo Set Global variables ani oka option untundi kada bhayya

akkada nenu munde anni values ichaanu....ala ichi package run chestunte its not picking up the variables in QA

but same thing Dev lo chesinappudu it worked for me....

FYI, I didn't migrate the package from Dev to QA. I've made changes directly in QA same as Dev...

Do you think that matters really?


btw SIT ante endi?
[/quote]

Systems Integration & Testing emo....

[loveindia]

[quote name='kumargadu' timestamp='1365435617' post='1303564287']
bros,
ma database size roju roju ki perigipootundi almost disk full aiepooindi , online check chesthey shrink is not a good option ani undi , Are there any other ways to reduce the size or do we have to add extra disk space?
[/quote]

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..

[deals2buy]

[quote name='DARLING...' timestamp='1365435551' post='1303564280']
Ya adi matter avtadi kada mari, akkada packages ikkada packages same undaali, for safer options we migrate the latest to test environment, so that no changes are skipped.

SIT antey system integration testing, idi oka environment nundi inko environment ki code movement or package movement appudu avi teeskuni changes apply avtunnayoo levoo check chestaam. just like rough notes.
[/quote]

same thing Dev lo work ainappudu QA lo enduku work avvadu bhayya?

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?
[quote name='loveindia' timestamp='1365435711' post='1303564298']

Systems Integration & Testing emo....
[/quote]ok...paina naa question ki answer cheppu

[littlemoon]

[quote name='kumargadu' timestamp='1365435617' post='1303564287']
bros,
ma database size roju roju ki perigipootundi almost disk full aiepooindi , online check chesthey shrink is not a good option ani undi , Are there any other ways to reduce the size or do we have to add extra disk space?
[/quote]

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 shrink our data and log file sizes..

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..

[Darling999]

[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]

painaa bhayya cehppina points anni kaakundaa. if any of your jobs are creating indexes on huge tables, then check those once. I got this issue previously, but could not found an answer, nenu ayitey autogrowth unrestricted petti vadilesaa. Appudu Index creation time lo db size almost 70Gb perigi create ayyaka adi malli decrease ayipotundi automatically. So just check with experts(MSDN forums) in case. Post your answer if you Find any.

Also shrinkin is Fine if yoy have unused space between the pages allocation. you can try the option releasing it to reduce the DB size that's suggested in the pop up for shrinking. there wont be any loss of data when you shrink the Db with unused space.