WQL queries in the console are translated to SQL and executed against the DB like any normal SQL query (you can see this in the smsprov.log on the site server) and thus there’s no additional overhead from a strict query perspective. There is some additional overhead for the translation to SQL and formatting for the console, but this is generally pretty low. If WQL queries had any huge perf impact, then your site would have constant issues since every collection is based on a WQL query.
Having said that, a poorly written query or one that returns huge amounts of data, whether in WQL or SQL, will always have a perf impact. Also, an undersized or poorly configured SQL instance will do the same. J From: [email protected] [mailto:[email protected]] On Behalf Of Poole, Richard Sent: Friday, July 18, 2014 5:20 PM To: [email protected] Subject: [mssms] Reports vs queries Happy Friday everyone, I unfortunately have someone in upper management that has been through the ropes with SMS 1.0-2003. They keep wanting reports from various things, but think all these custom requests are simple because all he knows is going into queries and pulling the data from there. I’ve been working from 2007-2012 and I thought the philosophy behind queries was that they pegged the SMSProvider and to not use them other than developing lists that could be used in collections. Is there any documentation on this being the case? My next plan of attack is to then use performance monitoring and run one of the queries I swear brings the server to its knees. Thanks in advance, Richard Poole
