Timeline for Default Schema Problems on server
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 12, 2020 at 14:33 | history | edited | Aaron Bertrand | CC BY-SA 4.0 |
deleted 7 characters in body
|
Jul 24, 2012 at 13:37 | comment | added | Glen Robson | I already have set the default schema for every user, but what im saying is if i remotly access the server from my machine i am connecting with the same username both on the server and on my local machine but i am getting different results on each machine? | |
Jul 24, 2012 at 13:33 | comment | added | gbn | So use synonyms to mask it. NoteI use schemas but I don't use default scheme for a user: can you simply set the default schema for everyone? | |
Jul 24, 2012 at 13:31 | comment | added | Glen Robson | The only schemas i have in my database are my schema (GLENSSCH) and dbo. And it would take months to change every single procedure, function and view within my database. That would not be possible. | |
Jul 24, 2012 at 13:28 | comment | added | gbn | @GlenRobson: a synonym is an alias for an object, as per my link. So your SQL_USER schema will resolve to your [DOMAIN\Glen] schema. Otherwise, fix the code | |
Jul 24, 2012 at 13:27 | comment | added | Glen Robson | Im sorry but that makes no sense to me | |
Jul 24, 2012 at 13:19 | comment | added | gbn | @GlenRobson: added a workaround... | |
Jul 24, 2012 at 13:19 | history | edited | gbn | CC BY-SA 3.0 |
added 239 characters in body
|
Jul 24, 2012 at 13:12 | comment | added | Glen Robson | I get that it is best practice but unfortunatly i did not write the views or stored procedures. There must be a way around this? | |
Jul 24, 2012 at 13:06 | history | answered | gbn | CC BY-SA 3.0 |