Your opinion is wrong. The question asks for defaults for this T-SQL code. The defaults are not stored in sys.parameters. They are only in the code definition in sys.sql_modules.definition.

 

The state department I work for has blocked all generative AI. I don't know why. It might even be blocked for all state departments. I don't have access to...

It's crazy these aren't parsed and maintained in a DMV for T-SQL procs, but they're not

The docs note this has default values for SQLCLR procs, not T-SQL ones.

SQL 2019:

 

SQL 2022

December 21, 2023 at 5:18 pm

#4350333

Thanks, fixed

Yeah, the parsing for the code formatting is that there are so many cases with the regex and replacement that I think we're fixing one thing but breaking another.

Bug filed...

I'll log a bug. I hope this is an easy fix.

We that's interesting.

OK, sorry, moving too fast this am. I missed that.

Test 2, space for table 1

SELECT [T1].* -- or could do [T2].*, not certain which table row you...

I think the formatting can be weird, but not seeing the issue.

Do you have a screenshot of what's broken/weird on your side? I'm chrome, 119.0.6045.200

test

SELECT [T1].* -- or could do [T2].*, not certain which table row you are trying to show, you may just want *

FROM [table_1] AS [T1]

INNER JOIN [table_2]...

test

SELECT [T1].* -- or could do [T2].*, not certain which table row you are trying to show, you may just want *

FROM [table_1] AS [T1]

INNER JOIN [table_2]...

Great points, and I think one of the great side effects of DevOps practices is logging and auditing of all actions.

Work and it's super non-intuitive. I want to love XE, but I find myself frustrated more than excited.

I like the default trace. I'm sorry to see it go