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
SQL Stored Procedure තමයි ඕකට හොඳම විසඳුම. client application එක slow වෙන්නෙ නෑ.machanla ubala hemotama thnaks a lot ..... mama den mokakda karanna ona ??? mage me wede karanna puluwan lesi widihak kiyanna program aka slow nowi
um.. how is this in anyway related to views degrading performance ??I don't think we are in the same page here. I’m not talking about the client end. Let’s say you have employee, project and department tables in your DB. Departments and Employees are assigned to projects. You want to get number of projects, completed by each employee. The only way to achieve this is to use a join. But lets say you have another column called project count, in the employee table which get incremented by 1 whenever a project get completed, using a trigger, of course. Now you can directly query the new column, without joining and you can yield results more efficiently. So no extra join algorithms needed to perform, just pulling the stuff from the base table. Please note that I’m not a DB savvy or anything.
I don't think we are in the same page here. I’m not talking about the client end. Let’s say you have employee, project and department tables in your DB. Departments and Employees are assigned to projects. You want to get number of projects, completed by each employee. The only way to achieve this is to use a join. But lets say you have another column called project count, in the employee table which get incremented by 1 whenever a project get completed, using a trigger, of course. Now you can directly query the new column, without joining and you can yield results more efficiently. So no extra join algorithms needed to perform, just pulling the stuff from the base table. Please note that I’m not a DB savvy or anything.
SP එකේ query 3ම ලියලා data process කරලා තනි recordset එකක් හැටියට report එකට එවන්නෙ. ඒක server side process එකක් හින්දා client slow වෙන්නෙ නෑ.machan...table diha balapan..SP liyala report ekata link karanna onet tun vidihakata neda..mama ape yaluvata kuwe sub report gahanna kiyala..eka attatama slow venava...ekata sollution ekak vidihata mama kuwe index karanna kiyala...
නෑ බං, SP එක ඇතුලෙ query 3 run කරල data ගන්නවා table 3න්ම. අරන් temporary table එකකට දානවා පෙන්නන් ඕනෙ පිලිවෙලටම. ඊට පස්සෙ ඒ temporary table එකේ තියන data යවනවා result data set එක හැටියට report එකට.tani record set ekak vidihata evala ape yaluva kiyana report format ekata ganna bane ban ? billno eka eka table ekaka nati unot rotation,return area blank..eka oya kiyana single sp + recordset ekena prepare karanna puluvanda?..ehema karat..client end eke report eken process venava neda?
that database certainly needs a redesign
slow databases can make your life a living hell... trust me when I tell you lolz.
its a best idea..but look when system using multi - users @ same time... trigger may be lock ur table for update..it may be concurring issue @ the end!!!
oh I see, yes, indeed what you say is true.View has a extra layer of processing so querying from a view takes more time than directly querying from the table. Its same as a join query I referred earlier. VIEWs generate data by algorithms(collection of JOINs,SELECTs,..etc) since they do not exists. Its good for security, role definition and etc. But since OP is more worried about the performance I think he should consider optimizing the design instead.
View has a extra layer of processing so querying from a view takes more time than directly querying from the table. Its same as a join query I referred earlier. VIEWs generate data by algorithms(collection of JOINs,SELECTs,..etc) since they do not exists. Its good for security, role definition and etc. But since OP is more worried about the performance I think he should consider optimizing the design instead.
