Some years ago, I purchased the domain name DataDude.com.au
I was thinking that I would pivot to being more of a data dude
I am never going to use it, I am open to suggestions.
Greg Harris
Harris Consulting Group Pty Ltd
g...@harrisconsultinggroup.com
www.HarrisConsultingGroup.com
That’s a pity. But you can, as you mention, have post deploy steps that put
them in place. Ideally though, they’d still come from something like Key Vault
instead of being in the scripts or in files somewhere.
Regards,
Greg
Dr Greg Low
1300SQLSQL (1300 775 775) office | +61 419201410 mobile
Thanks for the advice, Greg.
Unfortunately, the setup is "legacy" using SQL logins and AD auth is not an
option here. Deployment strategies are currently being investigated but it
looks like they may be going with the old TFS pipelines. I guess the actual
logins and assignment to roles would need
Hi Tom,
For roles and permissions, they should just go directly in the DB projects.
Nothing special about them.
Users/logins are different.
Ideally, you’d have AD or AAD based groups that are added to the roles, and
again they can go right in the project. If you’re looking after the DB or
Hello
I'm fairly new to Visual Studio sqlproj projects and was wondering what the
normal practice is for managing database security scripts (user logins,
users, roles, permissions).
I have seen some other projects here where the previous developers had the
create login SQL code for example in
