Comments
1 comment
-
Hi Aaron,
Thanks for the suggestion. That behaviour isn't actually a bug. At the start of the batch the only objects you can reference by name are stored procedures, since it's possible to execute a stored procedure without preceding its name with EXEC/EXECUTE if it's the first statement in a batch, hence you see that as soon as you enter something the list of tables empties. I've no idea why Microsoft chose to allow this although I'm sure there's probably some historical reason behind it going back to the days of Sybase or something.
Cheers,
Bart
Add comment
Please sign in to leave a comment.
Nothing big, but it would be nice to be able to look up table definitions quickly this way instead of having to do sp_help.
Thanks,
Aaron