Log in | Forgot Password | Register
What is OpenID?
OpenID is an Internet-wide identity system that allows you to sign in to many websites with a single account.
With OpenID, your ID becomes a URL (e.g. http://username.myopenid.com/). You can get a free OpenID for example from myopenid.com.
For more information visit the official OpenID site.
12 Posts in 12 Topics by 2 Members
Jump to:Limitations and Known Issues
DBSophic's professional support is available via these channels:
-
Send an Email to DBSophic's support team at support@dbsophic.com.
-
Register and post your question in one of the support forums. The DBSophic support team monitors the forums and will do its best to answer you promptly.
You need to register in order to post a message.
You can browse and read all messages anonymously.
Search the Frequently Asked Questions and the Limitations and Known Issues rooms for an answer before starting a new topic.
When contacting support, please provide as many details as possible regarding your issue, including O/S details, product version, and SQL Server version.
For licensing related issues, please attach the computer ID and license key (if available).
Support Forums » Limitations and Known Issues » T-SQL Parsing limitations
| Page: 1 | Go to End | |
| Author | Topic: T-SQL Parsing limitations | 583 Views |
-
T-SQL Parsing limitations
19 March 2009 at 11:29am Last edited: 19 March 2009 11:29am
The Qure parser does not support parsing and analysis of the following types of queries:
Queries that use quoted identifiers
Qure does not support parsing queries that use quoted identifiers for object names such as “Table1” instead of [Table1].
This is an inherited limitation as Qure cannot know each process’s run time QUOTED_IDENTIFIER setting.Dynamic queries in server side objects
A less common query writing technique involves dynamically creating the query as a string literal, and then using EXEC or sp_executesql to execute the string containing the query.
If this dynamic construction of the query is done at the application tier, Qure captures the final constructed query from the trace and then parses and analyzes it.
If the dynamic construction of the query is done in server side objects (such as stored procedures, triggers or functions), Qure is not be able to follow its construction or execution, and is therefore unable to analyze it.
The benchmark process however, executes and records batches that call the containing object, either directly or indirectly.Extended procedures and CLR objects
Qure does not analyze OLE automation (extended procedures) and CLR objects in the database.
All referenced objects in the queries that use OLE or CLR objects are analyzed, except for the expressions or clauses containing references to either the OLE or CLR objects.XML X-queries
Qure does not parse X-Query expressions and does not analyze any query that contains an X-Query expression.Column name resolution limitations
The following column aliasing syntaxes are not supported:> Aliases provided in an alias list.
For example, SELECT * FROM (<Sub query>) AS X (Alias1, Alias2…)> Aliases in DELETE and UPDATE using the proprietary additional “FROM” SQL Server syntax.
> Aliases derived from sub queries that use set operators such as Union, Except and Intersect.
For example, SELECT Column1 FROM (<Sub query1> UNION <Sub query2>) AS X.> Queries that contain any of the above syntax constructs are partially analyzed.
ODBC Date and time formats
ODBC specific Date & Time formats are not supported. For example, “{d '1998-02-23'}”
| 583 Views | ||
| Go to Top |
Currently Online: There is nobody online.
Welcome to our latest member: Anonymous user
Read Only
