Comments
Sort by recent activity
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...
hi @sdks if I've got it correctly, you're looking for a way to check whether SQL Prompt is enabled on suggestions and code analyisis, and then you'd like to disable those two options programmatically: [image] if so, there is a file called RedGate_SQLPrompt_CommonUI_Options_UIOptions.xmllocated into %LOCALAPPDATA%\Red Gate\SQL Prompt 9(because I've the version 9). You can find the two flags on it, as described here: [image] Changing it and restarting SSMS will maybe work (never tried before to be honest). Hope this helps / comments
hi @sdks if I've got it correctly, you're looking for a way to check whether SQL Prompt is enabled on suggestions and code analyisis, and then you'd like to disable those two options programmatical...
usually, when I receive that message there is a toggle for the error message. Without it, It's impossible to understand the reason why your SoC is not sending data. / comments
usually, when I receive that message there is a toggle for the error message.Without it, It's impossible to understand the reason why your SoC is not sending data.
Hi @Alexander_1983, did you try to expand the error detail below the message? / comments
Hi @Alexander_1983,did you try to expand the error detail below the message?
Using VSTS it's possible to query the histories also parametrising the query itself. However I don't know what's your one. / comments
Using VSTS it's possible to query the histories also parametrising the query itself. However I don't know what's your one.