Some questions refering to Custom Collections #776
-
Hi David, I have been waiting for this feature for some times and now that the feature is there I am very excited to set it up. I have been checking your Video this regard many times and followed you instructions step by step but unfortunately I still am puzzling around and it is unclear to me how things are working or maybe I am totally missing the point. Anyways I decided to open up this thread to get some better understanding. Sorry if the questions below might be a bit off or trivial but I really I am having difficulty to understand the process. I am not quite sure but I also think I have found a small (but important) bug in the Application this regard. If this is true or not, can be verified after I get a better understanding Question 1:
Question 2: A possible Bug in the application (which I mentioned above):
I certainly don’t save my custom SPs in the “master” database which in return means I am also not able to choose any one of them and this makes setting up the Custom Collection Feature for individual instances impossible. I hope now one can follow why I am asking the above questions. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Question 1 The custom collection stored procedure is created in the database that DBA Dash connects to. This refers to procedure that is going to collect the data from your monitored instances. e.g. sp_Blitz or whatever custom script you want to run. Question 2 The script generated when you click the "Get Script" button is to be run in the repository database only. There isn't anything here to run sp_Blitz as that will be run by the agent. The purpose of the script is to provide a place in the repository DB to store the data and a mechanism to handle the data import. If you setup a collection for all instances you are prompted for a connection. The only purpose of this is to populate the stored procedure drop down list. It's also used when you click the Get Script button. It doesn't influence where the agent will collect the data from in any way. If you don't want to create your custom collection SPs in master, you can change the source connections to have a different default database. Hope this helps |
Beta Was this translation helpful? Give feedback.
-
PS. The documentation for DBA Dash is also open source if you are interested in improving the documentation. e.g. |
Beta Was this translation helpful? Give feedback.
-
The links don't work on GitHub because they get redirected. Once the website is built the links work: Thanks for reporting issues - that's also useful. 😊 |
Beta Was this translation helpful? Give feedback.
Question 1
The custom collection stored procedure is created in the database that DBA Dash connects to. This refers to procedure that is going to collect the data from your monitored instances. e.g. sp_Blitz or whatever custom script you want to run.
Typically the agent will connect to the master database so you can either create the procedure there or alter the connection string for the source connection to specify a different default database.
Question 2
The script generated when you click the "Get Script" button is to be run in the repository database only. There isn't anything here to run sp_Blitz as that will be run by the agent. The purpose of the script is to provide a place in the…