Feature request:TMSQuery.GenerateParametrizedSQL
Hello AndreyZ,
I think this is the right way to prioritize the user requests.
But I have to ask another question: I've seen that slow queries with parameters on my previous version which was ADO-based and changed many queries to simple sql-text without parameters (therefore this feature request has not the highest priority for me). If that is a ADO/OLEDB-problem, possibly it's better to make a SpecificOption for MSSQLprovider, which you can faster implement and test?
What is your experience (as devart) in your other products (.Net, DBExpress): Are there parameters on SQLServer-queries also bad?
If not: Can there go something wrong in the implementation of the parameters for the MSSQLProvider?
I think this is the right way to prioritize the user requests.
But I have to ask another question: I've seen that slow queries with parameters on my previous version which was ADO-based and changed many queries to simple sql-text without parameters (therefore this feature request has not the highest priority for me). If that is a ADO/OLEDB-problem, possibly it's better to make a SpecificOption for MSSQLprovider, which you can faster implement and test?
What is your experience (as devart) in your other products (.Net, DBExpress): Are there parameters on SQLServer-queries also bad?
If not: Can there go something wrong in the implementation of the parameters for the MSSQLProvider?
This problem is connected with the specifity of SQL Server. As you can see in the first post of this topic, brace wrote examples of SQL code that are sent to SQL Server in both cases (with and without parameters). The point is that SQL Server executes some queries faster if they don't have parameters (i.e. they have plain text).
Re: Feature request:TMSQuery.GenerateParametrizedSQL
Hello, since I need to close an internal request could you please update me on this feature: is it planned or not?
Re: Feature request:TMSQuery.GenerateParametrizedSQL
We have this feature in our tasks, but we do not plan to implement it this year.
Re: Feature request:TMSQuery.GenerateParametrizedSQL
Thanks for the reply.
Re: Feature request:TMSQuery.GenerateParametrizedSQL
Just keeping an eye on this. Any changes in plans about alowing to send non parametrized querise to sql server even Parameters are used?
Re: Feature request:TMSQuery.GenerateParametrizedSQL
any progress on this task? Thank you.
Re: Feature request:TMSQuery.GenerateParametrizedSQL
Hello,
We implement new features depending on their complexity and relevance, and since this feature is rather laborious and unclaimed, we don't plan to implement it in the nearest future.
We implement new features depending on their complexity and relevance, and since this feature is rather laborious and unclaimed, we don't plan to implement it in the nearest future.
Re: Feature request:TMSQuery.GenerateParametrizedSQL
THank you. As far per "laborious" i am not sure it is. If it is done for SDAC only.
I didn't research too much anyway i noticed that MacroByName is drastically faster than ParamByName only in some compelx queries so manaully replacing ParamByName with MacroByName is an option.
This faeture could anyway give extra speed for free to all the users that stick with ParambyName as the only way to do things.
This seems interesting:
http://stackoverflow.com/questions/1093 ... parameters
I didn't research too much anyway i noticed that MacroByName is drastically faster than ParamByName only in some compelx queries so manaully replacing ParamByName with MacroByName is an option.
This faeture could anyway give extra speed for free to all the users that stick with ParambyName as the only way to do things.
This seems interesting:
http://stackoverflow.com/questions/1093 ... parameters
Re: Feature request:TMSQuery.GenerateParametrizedSQL
Hello,
If this feature will be added - it will be added for all the DAC products. Therefore it is a rather time-consuming feature.
Value substitution to a SQL query instead of parameters (or macros), as well as the use of the RECOMPILE option, will help increase performance in queries, that are executed rarely. If a query is often executed, and parameters often change, then the use of these approaches will decrease performance in comparison to the use of parameters.
If this feature will be added - it will be added for all the DAC products. Therefore it is a rather time-consuming feature.
Value substitution to a SQL query instead of parameters (or macros), as well as the use of the RECOMPILE option, will help increase performance in queries, that are executed rarely. If a query is often executed, and parameters often change, then the use of these approaches will decrease performance in comparison to the use of parameters.