Ed Wagner (3/14/2014)

---

Grant Fritchey (3/14/2014)

---

Yeah, that one is killing me. Vague weirdness, badly edited execution plans quite literally...

Well, that's an indication anyway. Parse time includes time to check the cache, so you get some idea of how trivial that process can be. It won't always be though.

Yeah, that one is killing me. Vague weirdness, badly edited execution plans quite literally changing everything we can...

The answer is in the sys.dm_db_index_physical_stats as was outlined in the query above. You can get targeted statistics on a given index, or get all statistics on all indexes. Read...

I know you said you don't want to change the code, but it looks like there might be problematic bits in there. However, without an execution plan, I've got nothing...

Yeah, I'm with Gail on this. I spotted the one issue, but I'm pretty sure you have others. But working off this vague set of descriptions the best I can...

Hmmm... Not crazy about that approach in the script. Allen White has a script he uses to do the same thing. You might search his blog. I'll bet it's more...

All the memory is not too much. SQL Server has limits to the amount of memory it can use. You can see that here in the documentation. You'll want to...

You don't have b.Rank as one of the columns defined in the SELECT list that you're selecting from.

This is not a good practice, for some of the reasons you're hitting...

george.auckland 44813 (3/13/2014)

---

I did that. Here is the full function (Thanks for your help by the way):

USE [CTM_Reporting]

GO

/****** Object: UserDefinedFunction [dbo].[ufn_Banner_Orion_Employee_Comparison_parser_v2] Script Date: 3/13/2014 11:57:36 AM...

You have to build the string. Just referencing the parameters won't work.

I'd suggest trying some indexes on the table and using a JOIN to do the UPDATE.

You have parameters that you're passing values to and then those parameters are used in your SELECT statement to return the values passed. That's how parameters work. What you're...

It's a security error that's basically preventing you from making a series of calls to the OS. To run it, you have to do what it's asking for.

This is a VM running on Azure, which means, technically, the HyperV hypervisor although things are a little different...