Yeah, I've got them ethics things too. That and there seem to be laws against using sticks on the students. When did that happen?

Just so long as you quantify your post to read "some knowledge" because I'm basically a newbie on SCOM myself. I've been working with it for, probably close to three...

Try modifying this query to exclude specific tables:

SELECT QUOTENAME(TABLE_SCHEMA) AS schemaname, QUOTENAME(TABLE_NAME) AS name FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = 'BASE TABLE'

Quick and dirty would be like this, Jeff will come...

Some operation within your code is attempting to perform math functions and it's dividing by zero. You need to determine which field is causing the problem. Without your code, data,...

I don't know if there is another forum for it. I've posted my own questions here.

Getting specific information regarding SQL Server and SCOM is tough. Definately you want to look...

But, do it this way, and the execution time decreases radically. The number of reads is slightly higher though... for whatever that's worth:

SELECT a.[AddressID],

...

Neither one is the very best way to do things, but I took this query and ran it against Adventureworks. The execution plans were identical. Both used Index Seeks. The...

Use it all the time, but like this:

UPDATE Table1

SET Field2 = b.Field2

FROM Table1 a

JOIN Table2 b

ON a.Field1 = b.Field1

I don't know that the ANSI standard on the join...

I wasn't entirely happy with it either. Not too to be salesman, but Red Gate's SQL Prompt does everything you're looking for. I'm still planning on using it going forward.

Yikes. If they're teaching you to use the IN clause with a sub-select, time to run. Get them to hire Jeff Moden or one of other people from here to...

You should look into the BOL and check out how to do ANSI standard joins. It'll make your code more readable and can improve performance by limiting data at the...

I strongly recommend against using the old style joins. You really can run into trouble and they're not supported in every instance in SQL Server 2005 & above. See here...

If I have to pick only one, I'd go with consistency. Once everything looks and acts similarly (even if poorly), it's much easier to work on the quality and raise...

I suspect you're also getting recompiles during execution. These will kill performance. You might want to use the KEEPFIXED PLAN hint internally on the queries, but not on the proc...

Sorry, I must have missed the execution plan earlier.

These are going to prevent the code from using indexes:

isnull([@lv_processComparisonDate],[@lv_processCOBdate])<=isnull([MARKET_RISK_DB_US].[publish].[DIM_STRATEGY].[EFCT_END_DT] as [selStrategy].[EFCT_END_DT],'9999-12-31 00:00:00.000'

Also, based on the fact that there are so many...