This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We recently went through a migration between SQL Server instances (2008 to 2016). On the day that we cut over I expected to be able to change the connection string of the Gallery Connection to point to the new server. However 3 day later we had found that it hadn't actually made the changes at the workbook level on scheduled jobs. Am I misunderstanding how this is supposed to work?
I will also note that every time we publish jobs, we remove the gallery connection assets (for a totally different reason), as I understand it removing this dependency means that it will always call to the gallery? Do I have this backwards? If I am correct, what I imagine might be happening is even though we remove that dependency on the gallery, it still saves the dependency on the scheduled job? Or did I really mess something else up?
I had about 75 jobs that I had to go through and put a new gallery connection in so that work is done.
But to respond to your suggestions. 99% of these jobs had gallery connections, we manage all of the really important stuff through a service account so as part of our peer review/scheduling process, I move everything to gallery connections. The ODBC connection comment has me thinking... We are using OLE connections because they seem to be faster and more reliable. Could this be an issue?
I will probably end up testing this suggestion below with a demo workbook. But for clarification, I am misunderstanding how this is supposed to function? Should I be able to adjust the gallery connection strings and that is passed through to the jobs below? Because I can stop thinking that no problem, I just need to know lol.