Timeline for Why Does Microsoft SQL Server Management Studio Keep Creating Table Aliases?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 27, 2017 at 6:53 | comment | added | Tony | Randolph West: I understand why it would do it to avoid name conflicts but there are no conflicts. As I said, it seems to do it for no apparent reason (other than to annoy me). I have been opening in Script View to remove the aliases and the view works fine. ypercube: It won't change aliases I've created but if I remove the aliases it creates the view will save and execute fine. It will, however, put them back if I re-open the view in Design View. | |
Jan 19, 2017 at 19:46 | history | tweeted | twitter.com/StackDBAs/status/822168404190789635 | ||
Jan 19, 2017 at 13:06 | comment | added | ypercubeᵀᴹ | Does it do this (change your code) if you open existing queries where you have defined your own aliases? | |
S Jan 19, 2017 at 10:36 | history | suggested | Ian_H |
Generic tag & topic tags added
|
|
Jan 19, 2017 at 9:39 | review | Suggested edits | |||
S Jan 19, 2017 at 10:36 | |||||
Jan 19, 2017 at 8:15 | answer | added | Andriy M | timeline score: 5 | |
Jan 19, 2017 at 6:59 | history | edited | user1822 | CC BY-SA 3.0 |
added 30 characters in body; edited tags
|
Jan 19, 2017 at 6:47 | comment | added | Randolph West | This behaviour is by design, to avoid name conflicts. If you want to stop this from happening, you will have to modify views in T-SQL, by right-clicking on the view name in the Object Explorer, and scripting the view as ALTER. | |
Jan 19, 2017 at 3:32 | review | First posts | |||
Jan 19, 2017 at 7:58 | |||||
Jan 19, 2017 at 3:29 | history | asked | Tony | CC BY-SA 3.0 |