Comments
Sort by recent activity
Resently I also began to get this exact error. I have just updated SQL Prompt to 10.13, already have the newest SSMS 18.12.1, and Excel is 2016 64 bit 16.0.5369. And i still got the error. / comments
Resently I also began to get this exact error.I have just updated SQL Prompt to 10.13, already have the newest SSMS 18.12.1, and Excel is 2016 64 bit 16.0.5369.And i still got the error.
Hej Robert
We have tried source control on a named schema.
And we are not convinced.
Then we are using objects not in the schema, source control keep asking, if these objects should be source controlled.
Then we have to remove a check mark and press ok, some day someone forgets this.
We have searched for how to change the default behavior, without luck.
/Jesper / comments
Hej Robert
We have tried source control on a named schema.
And we are not convinced.
Then we are using objects not in the schema, source control keep asking, if these objects should be source contr...
Thanks Robert,
This is very nice to know.
However, there is a reason more for option 2.
Security, "noob" SQL developers having to many rights on a production database.
Development of some Stored Procedures needs high privileged rights.
Any comments on option 2?
/Jesper / comments
Thanks Robert,
This is very nice to know.
However, there is a reason more for option 2.
Security, "noob" SQL developers having to many rights on a production database.
Development of some Stored Pr...