Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.
Course Of The Month
3 days, 12 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Strange SQL view, where clause, COALESCE perfomance issue
Posted on 2014-12-18
I have a weird sql issue.
I don't have control over these SQL statements. They are created and executed (behind the scenes) by an application (Sage CRM).
So please don't ask me to change the SQL statement because I can't and the product manufacturer (Sage CRM) says the issue is with my sql server...
The only reason I know what the sql statement looks like is because it times out and an error gets written to a log file.
This SQL statement takes 4 minutes to return 792 records -
SELECT * FROM z_vmailinglistreport WHERE
(( COALESCE(comp_type, '') = N'rescontractor' ) )
AND ((pers_secterr = -2034921070))
AND coalesce(pers_cstatus,'') = 'Active'
If I use the SELECT statement from the view and add the WHERE clause it runs in 1 second.
If I remove either one of COALESCE functions it runs in 1 second.
Any ideas?
Thanks,
Kevin.
I don't have control over these SQL statements. They are created and executed (behind the scenes) by an application (Sage CRM).
So please don't ask me to change the SQL statement because I can't and the product manufacturer (Sage CRM) says the issue is with my sql server...
The only reason I know what the sql statement looks like is because it times out and an error gets written to a log file.
This SQL statement takes 4 minutes to return 792 records -
SELECT * FROM z_vmailinglistreport WHERE
(( COALESCE(comp_type, '') = N'rescontractor' ) )
AND ((pers_secterr = -2034921070))
AND coalesce(pers_cstatus,'') = 'Active'
If I use the SELECT statement from the view and add the WHERE clause it runs in 1 second.
If I remove either one of COALESCE functions it runs in 1 second.
Any ideas?
Thanks,
Kevin.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
2-
2
- +1
7 Comments
Active today
The COALESCE (or any other function) used on a column will prevent SQL from doing an index seek for that column. Thus, even if the tables are perfectly indexed for the query, SQL won't be able to take advantage of it.
The only way to get the best performance out of such queries is remove the unnecessary COALESCE (NULL will never be =, <>, < or > any value anyway, so converting null to '' isn't needed):
WHERE
( comp_type = N'rescontractor' )
AND ((pers_secterr = -2034921070))
AND pers_cstatus = 'Active'
The only way to get the best performance out of such queries is remove the unnecessary COALESCE (NULL will never be =, <>, < or > any value anyway, so converting null to '' isn't needed):
WHERE
( comp_type = N'rescontractor' )
AND ((pers_secterr = -2034921070))
AND pers_cstatus = 'Active'
Thanks for the info.
Any idea why the query runs almost instantly when I take the select statement from the underlying view and add the where clause to it (with the COALESCE) ?
Or if I add the where clause to the view it runs instantly as well.
Thanks, Kevin.
Any idea why the query runs almost instantly when I take the select statement from the underlying view and add the where clause to it (with the COALESCE) ?
Or if I add the where clause to the view it runs instantly as well.
Thanks, Kevin.
Active today
You need to create a function based index. But there is a catch, SQL Server does not support it natively like it is in Oracle or Postgresql. There is a workaround. Create two computed column. Here is an example for one, comp_type:
ALTER TABLE z_vmailinglistreport ADD COMPUTED_comp_type AS COALESCE(comp_type, '');
-- And then create an index on the computed column:
CREATE INDEX ix_z_vmailinglistreport_COMPUTED_comp_type ON [z_vmailinglistreport](COMPUTED_comp_type);
Hi Lee, it is 7.2e
Just to clarify, the issue happens even when just running the query in SQL Server Management Studio.
So unless Sage changes the way they use the COALESCE feature I may be stuck.
I actually changed the view around to pre-filter the on pers_cstatus = "Active".
This took that criteria out of the report and resolved the issue for now.
But I'm still curious about why the view and where clause behave the way they are behaving.
Thanks,
Kevin.
Just to clarify, the issue happens even when just running the query in SQL Server Management Studio.
So unless Sage changes the way they use the COALESCE feature I may be stuck.
I actually changed the view around to pre-filter the on pers_cstatus = "Active".
This took that criteria out of the report and resolved the issue for now.
But I'm still curious about why the view and where clause behave the way they are behaving.
Thanks,
Kevin.
Active 6 days ago
Believe me I know all about Sage using the coalesce function. It's caused me no end of problems in other areas of CRM. I'm guessing this is a report and the fields that CRM is having issues with are the search criteria fields in the report builder.
Are you allowing the users to choose their own values for the search criteria or are they fixed?
Are you allowing the users to choose their own values for the search criteria or are they fixed?
Featured Post
Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Load balancing is the method of dividing the total amount of work performed by one computer between two or more computers. Its aim is to get more work done in the same amount of time, ensuring that all the users get served faster.
A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL).
Depending on business requirements, a single Stored Procedure can return differe…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Suggested Courses
Course of the Month3 days, 12 hours left to enroll
691 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.