Strings are supposed to be surrounded with single quote marks. Quoted Identifiers allows you to put double quote marks around reserved and key words to use them as objects within...

fn_listextendedproperty, as you've found, only returns values where those values exist. What you'd need to do is combine the output of that query through a left join with a valid...

Theres a catalog view sys.extended_properties. You should be able to pull it right out of there.

You could output as XML and then pass it on to the presentation layer, but it'd probably be a lot easier overall to format the output on the app.

Cool, 128 character three place numbers. I use those all the time.

I like Mark's because it will only return those customers who have orders in all the included years. Much more precise.

It's hardly optimal, but you could:

SELECT...

FROM...

WHERE YEAR(OrderDate) IN (2001,2002,2003,2007)

You could add those values to a temp table & join on it. That would probably be better than than in IN...

My two cents, use the stored procedure. Cascading deletes is extremely unforgiving. That can be good, but it can be bad. As long as you've got appropriate constraints in place,...

I did just a bit more searching. I wasn't sure if it was possible to identify the proc you're in, let alone that proc that called you. If you look...

I've never heard of such a thing. You could simply add a parameter to your function and pass in the calling procs name. It'll be interesting to see if someone...

You may run into problems with this:

FORMAT(BUMetrics.ProjectCompletionDate, 'mm') AS MONTH, FORMAT(BUMetrics.ProjectCompletionDate, 'yyyy') AS YEAR

That's not TSQL syntax.

Yeah, I would have expected to see it begin offering completions when you were typing the schema. That's what I see on my machine. Are you using the November CTP?

I'm a little confused. You don't have any kind of WHERE clause on your queries.

This will be updating all records in the table where the join criteria is true, if...

You should try enabling the code and getting an estimated execution plan. That will tell you where the problems are.

Most likely you'll see that you're getting a table scan.

Holy cow. We've been lucky so far then. We've been naming the project after the database. What a mess.

With the initial release, I did find that we were hacking the...