Comments
Sort by recent activity
I will host a SQL Clone vs Containers session ("The SQL Clone Wars and rebellion of Containers"), but unfortunately, it will be in held in Italian. / comments
I will host a SQL Clone vs Containers session ("The SQL Clone Wars and rebellion of Containers"), but unfortunately, it will be in held in Italian.
Hi there! here is my two cents:
SQL Prompt article https://www.red-gate.com/hub/product-learning/sql-prompt/sql-productivity-with-sql-prompt
Two calls for research and feedback (SQL Prompt and Change Automation)
Sessions in SQL Sat Italy series
One session in DevOps@Work in Rome
Some meetup (I keep speaking about automation)
That's it! Happy new year guys! / comments
Hi there!here is my two cents:
SQL Prompt article https://www.red-gate.com/hub/product-learning/sql-prompt/sql-productivity-with-sql-prompt
Two calls for research and feedback (SQL Prompt and Chan...
Hi @bitshift2, choosing a "repo-style" is something which is related to source controlling your database, not related to the production environment you're working on. I suppose that this topic should be covered with a deep discussion on your team, about how to manage source control and branching style of your repositories for the databases themselves. If I got it correctly, you need to answer some questions, like the following ones:
is the database "codebase" the same across "some" database?
will you deliver a single database with changes in different installations?
how will you automate release processes and what is the toolset you're using (or is available for you) right now?
and si on, they are just some example. Covering this topic is a long-term process within your team and that should be made with your teammates, too. / comments
Hi @bitshift2,choosing a "repo-style" is something which is related to source controlling your database, not related to the production environment you're working on. I suppose that this topic shoul...
Hi @jornvango SQL source control, as you know, lets you link a single database to the underlying source control manager. Jobs are stored on msdb, but that database is strictly related to the environment where SQL server has been installed on. Since jobs are items that could be different in every production environment (at least test and prod) also for configurations like connstrings, I suggest you to create a folder in your SCM and put the generated scripts there. We're managing those file by customer (a folder per customer) and we're periodically scripting jobs with dbatools.io (http://dbatools.io) powershell cmdlets, syncing them for each change. Hope this helps / comments
Hi @jornvango SQL source control, as you know, lets you link a single database to the underlying source control manager. Jobs are stored on msdb, but that database is strictly related to the enviro...
Here to help, does it work for you if we meet the next week? 😁 / comments
Here to help, does it work for you if we meet the next week? 😁
Lol. DBAle it's me :-) / comments
Lol. DBAle it's me :-)
Welcome Roseanna! Glad to meet you online (for the second time, actually :-) ) / comments
Welcome Roseanna! Glad to meet you online (for the second time, actually :-) )