Latest ads
-
Gemini AI PRO 18 months Offer- Hawaka
- Updated:
-
koko account
- DasunEranga
- Updated:
-
koko account
- DasunEranga
- Updated:
SQL SEVER
- Thread starter ad.hasareli
- Start date
Oh..man..he talks to me via FB and i gave some instruction..he said its ok..i think he understand the way to solve it. Hope he will solved it.
Oh..man..he talks to me via FB and i gave some instruction..he said its ok..i think he understand the way to solve it. Hope he will solved it.
hey. thats great to hear.
thanks for you help..
wede hari nam tamai ath aka hari nehe machanla moko aka mara slow....repot aka load wenna 8sec witara yanawa I3 lap akaka tawa issaharata 1hr witara yawi report aka load wenna so aka hariyane nehe 
something seriously wrong in your database design to have data stored like this.
Anyway, use a temporary table at the client end to store data and build the report from that or use a mssql stored procedure to return only the needed dataset to the report.
Anyway, use a temporary table at the client end to store data and build the report from that or use a mssql stored procedure to return only the needed dataset to the report.
godak data tibboth join slow wenawa. wena widihakata implement karanna balapan.
e.g: use a single table with all the columns from the 3 tables + one column to identify whether it belongs to bill, rotation or return item.
wede hari nam tamai ath aka hari nehe machanla moko aka mara slow....repot aka load wenna 8sec witara yanawa I3 lap akaka tawa issaharata 1hr witara yawi report aka load wenna so aka hariyane nehe
machan DB eka normalize karapan. Speed karanna ona nam JOIN tables adu karanna ona. Query optimization kiyala wenama subject ekakma thiyenawa..podi research ekak danna.
Why dont you try a SIMPLE VIEW, As these db experts says. i think that also could help you,
You mean VIEWS like in MySQL? But isn't the performance degrade since the data generation is dynamic?
FYI: I have no experience in SQL Server.
its not a performance degrade as the server returns the required data without the client having to process it at the client end.
wede hari nam tamai ath aka hari nehe machanla moko aka mara slow....repot aka load wenna 8sec witara yanawa I3 lap akaka tawa issaharata 1hr witara yawi report aka load wenna so aka hariyane nehe
Machan..mama oke data normalize karana eka gana kuwe natte eka danatama uba project eka hadala nisai..attatama DB tables perfectly normalize vela na..eka tamai oya vidihata data duplication ekak dakinna puluvan...eka eka entities vala header details kiyala table devide karanna balapan..
attatama uba oka HND project ekak kuwa nisa mama echchara eka gana pannuvve na..mokada live yanne nati nisa..et live yanavanam oke design eka antimai...
anyway..oya report ekata data enne only per bill no as user selected...then u can have an inquiry for than use report....if you use such as inquiry for represent data...u can use LINQ inside the code for separate data for 3 different grids by using single query..
Bt the Db problem is exist as same coze its query cost is high ..
as per you wish ..u can do it!!!
wede hari nam tamai ath aka hari nehe machanla moko aka mara slow....repot aka load wenna 8sec witara yanawa I3 lap akaka tawa issaharata 1hr witara yawi report aka load wenna so aka hariyane nehe
uba table index karala baluve nadda?
machanla ubala hemotama thnaks a lot ..... mama den mokakda karanna ona ??? mage me wede karanna puluwan lesi widihak kiyanna program aka slow nowi
machanla ubala hemotama thnaks a lot ..... mama den mokakda karanna ona ??? mage me wede karanna puluwan lesi widihak kiyanna program aka slow nowi
oka report ekakma venna oneda machan!!
bill no eka dammahama anit details grid 3ka pennuvot madida....mata hitenne ee vage ekak tama vade goda daganna puluvan..eth ube project eke tiyenavanam oka report ekak venna one kiyala..poddak hitanna venava
