View Complete Post
I have an OLE DB source in a data flow task. The connection is pointing to a SQL Server 2008 instance. My SQL works fine when I click the preview button. Now I need to make it parameterized by adding a question mark in my where clause.
After doing so & clicking the Parameters button, I get the error described in
this post . When I try to do what's described therein to correct the problem (click the "build query" button), I get the error "The PIVOT SQL construct or statement
is not supported."
I can't make this query an expression; it's simply too complex to maintain that way (besides, just pasting it into an expression builder window and trying to evaluate
as is doesn't work - can't evaluate).
So the question is, how do I parameterize a query? And why does SQL here work so radically differently from SQL in an execute SQL task?
I'm using Enterprise Library Logging feature for logging. The issue i am facing is when the Logging message is too large(more than 65534 chars) ,complete data is not logged in the Formatted Mesage column which is of data Type nText .
I am able insert complete data if i try inserting from Sql insert Query from sql management studio. Do i need to add any attributes to data base listener or do i need to change the sp.
Is there any way to increase the WriteLog stored proc param size in EnterpriseLibrary.Logging config file ? . Please let me know.
Thanks In Advance.
LINQ to Objects and LINQ to Entities have an arsenal of Standard Query Operators that operate on sequences to perform a wide variety of operations.
MSDN Magazine March 2008
Find out the best way to store large amounts of XML data in SQL Server, along with the performance implications. What's the maximum length of an XML query to SQL Server in a URL?
Edited by Nancy Michell
MSDN Magazine May 2003