Comments
Sort by recent activity
Expands "advanced options", whoops with joy.
Annoyed with myself that I hadn't checked advanced settings earlier [image] / comments
Expands "advanced options", whoops with joy.
Annoyed with myself that I hadn't checked advanced settings earlier
Yes it does, thanks for prompt response / comments
Yes it does, thanks for prompt response
I have the latest version of SQL Generator installed and this issue still exists [image] I'm trying to clone a production database with masked data therefore referencing a source database to push to a destination database. The odd thing about this behaviour is the GUI will at least present the data from the source so it is able to handle the non-dbo location yet the script still fails because it isn't in dbo. I'm intending on working around this by putting dbo synonyms in the destination database so I'm not interfering with production but this isn't ideal.
Is there any progress on fixing this? / comments
I have the latest version of SQL Generator installed and this issue still exists I'm trying to clone a production database with masked data therefore referencing a source database to push to a des...
Thanks for that - I am aware of this functionality, I use to switch between my sysadmin permissions and developer permissions. The limitation with that is my credentials on TFS need to have permissions on the machine I'm running SSMS from (which they don't). I'll put it into context properly....
We have a hosted client environment, our internal domain does not have a trust with the hosted domain by design. Consequently, I cannot use any of my logons from the hosted domain to access the internal domain.
On hosted domain, I used hosted\JJB7 but internally I used internal\JJB7. Visual Studio it's simple, it attempts single signon and when it can't find hosted\JJB7 asks for my credentials, I can't do that (so it seems) with SQL Source Control? / comments
Thanks for that - I am aware of this functionality, I use to switch between my sysadmin permissions and developer permissions. The limitation with that is my credentials on TFS need to have permis...
james.billings wrote:
ref. SDOC-1428
Thanks for confirmation James, where would I find this? / comments
james.billings wrote:
ref. SDOC-1428
Thanks for confirmation James, where would I find this?
Ah, I made the mistake of searching through google and NOT through the forums :oops: found the answer to my question here / comments
Ah, I made the mistake of searching through google and NOT through the forums :oops: found the answer to my question here
I've come across a similar issue in my team, stumbled on this post and have fixed my issue as a result, thanks for the help. We've had to source control some databases in production as we don't have development / uat versions of them....yet. This issue doesn't arise in our dev area since my guys all have sa access to that box.
What I would add for anyone who stumbles across this, is that since tempdb is recreated every time SQL restarts, you will need to apply the required permission every time SQL is restarted. Easiest way is to have the permission applied by a SQL Agent job with a schedule of "Start automatically when SQL Agent starts". / comments
I've come across a similar issue in my team, stumbled on this post and have fixed my issue as a result, thanks for the help. We've had to source control some databases in production as we don't ha...