Orlando Colamatteo (6/23/2015)

---

Nope...the same issue persists with stored procedures but to a far, far, far...

Or of course you could just call a stored procedure and avoid this issue correct?

Good to know.

I'd point out that if someone's application is calling the same query repeatedly in a tight loop you might have a design issue though. You likely need...

It usually does a pretty good job. Until the code gets more complex, that's where I usually need to spend some time on it to try and eliminate the...

Jeff Moden (11/13/2014)

---

Perhaps it's not even an LDAP limit. Perhaps it's as simple as a DOS buffer limit, which can be easily overcome though the use of the ancient,...

You just need to pick a single unique field like user name, specify an order by on that, then you can just use the last value returned as the input...

Thank you for your suggestions, but I've about come to the conclusion that there is no way to do this. The problem being that I need access to the...

Yeah, I was trying to avoid that since it would add more complexity on the SQL side. There are currently different grouping criteria that are handled in formulas within...

Well, the simplest way would seem to be to just duplicate the SQL structure and code then have the application use an appropriate connection string depending on which country the...

There are other considerations beyond performance alone that discount the use of dynamic SQL. Speaking of writing it "right" in the first place.

Never say never, but it is something...

I know what you're saying, but I did a quick test loading 1.2 million rows to a test table which is about 10x what the production table should ever be...

The bulk of the execution plan cost comes out to a clustered index scan on the primary table. It's more than sufficient for our needs.

If I get the chance...

This has always been a sticking point for me, it always seemed to lead to "dirty" solutions. This is an approach I came up with to accommodate a flexible...

You could create the table with a placeholder name you generate, then use sp_rename @generatedName, @userName; to pass the user defined name as a parameter so that you...

I have a number of .Net applications utilizing the UDTT's to pass variable numbers of "parameters" to stored procedures. I haven't run into any problems, other than someone forgetting...