Koen Verbeeck (3/28/2012)

---

Good to see questions on SQL Server 2012.

I did find the question itself poorly phrased, because of the use of "other" and the general term "options".

When I look...

A late reply but the solution from Michael Rybicki worked perfectly for me as I was experiencing the exact same error on a large OLTP database on SQL 2008 R2....

It is NOT a SQL Server or RAM issue it is a application code or SQL code issue. You will need to research the cause of the deadlocks (i.e.,...

Are you trying to output @contactid?

Generally, using stored procedures within an SSIS package is a very, very, very poor idea. However, since it is a source, it...

Yes, all data used within the package such as the data source and look-up transformations reside within the RAM, memory cache, or persistent cache on the SSIS server.

If I extend...

An interesting and article; the applicability of which seems to become more poignant each year.

http://www.jstor.org/pss/98663

Nope, they will both function essentially the same. AFTER is generally used (in my experience it may have other, better uses) when there are multiple SQL statements and you...

FOR is for an action (Insert, Update, whatever). AFTER waits for all parts of the SQL clause to complete, that is for all conditions to have been met. ...

This might be of help...

http://support.microsoft.com/kb/926623

Also, on the SQL Server browse to C:\Program Files\Microsoft SQL Server\90\Shared\ (or wherever you've installed the SQL binaries). Find the file called: sqlmgmprovider.mof. Rename...

I assume creating a different view or changing the application logic are not acceptable options. So...If you know when the application will re-alter the view, you could schedule a...

Hmm

You can preview the report from within Visual Studio (versions 2000, 2005, and 2008) (assuming you have a connection to your database(s)). If you wanted to preview the report...

Interestingly, running it in my test database it returned in a single query window. Regardless of how it is run, all as a single query, each separate, in different...

It seems that you are correct. The only solutions appear to be creating a wrapper of some sort, which is way beyond budget and scope. I hope this...