May 13, 2022 at 10:27 am
We enabled / created SSISDB in one of our non-prod environments before we discovered we aren't allowed to use SSISDB on our servers (long story, don't ask). Now I'm trying to figure out if we can just delete the database or if there is something else we need to do in order to properly remove it.
All the articles Google points me to talks about cleaning up old projects and data in SSISDB. I can't find a single one about dropping / deleting / removing SSISDB itself.
Does anyone know if it will cause any problems if I just drop the database?
May 13, 2022 at 2:49 pm
We enabled / created SSISDB in one of our non-prod environments before we discovered we aren't allowed to use SSISDB on our servers (long story, don't ask). Now I'm trying to figure out if we can just delete the database or if there is something else we need to do in order to properly remove it.
All the articles Google points me to talks about cleaning up old projects and data in SSISDB. I can't find a single one about dropping / deleting / removing SSISDB itself.
Does anyone know if it will cause any problems if I just drop the database?
I can't imagine any issues at all, though it's not something I have ever done. I'd be tempted to take it offline for a week or two first, just in case something unexpected happens and it needs to be reanimated quickly (please post if it does, as it would be interesting to know).
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 13, 2022 at 5:45 pm
You also need to remove the SSIS maintenance agent job - but other than that there shouldn't be any issues. That system will still think it has been configured though - not sure what would happen if you tried to re-enable it again.
It's too bad, I know you have had a lot of issues with SSIS in the past and the recommendations have all been to upgrade to use the catalog.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 24, 2023 at 1:30 pm
The question is a bit old, but in case it can help someone else, here is what I did to disable SSISDB Catalog.
In SSMS go to Integration Services Catalogs folder, right click on the SSIDB catalog and choose Delete.
It will drop the catalog, drop the SSISDB database and drop the maintenance Job.
It will allow you to re-create/re-enable again in the future if needed.
English is not my native language... so, you know... sorry in advance 😉
March 3, 2023 at 9:35 am
This was removed by the editor as SPAM
March 15, 2023 at 7:23 pm
I deleted SSISDB and now I canot create a new one.Just wanted to ask you here what should I do but...I restarted the SQL Server Integration Service only allows to create again a new SSIDB.
March 15, 2023 at 8:25 pm
Did you delete the SSISDB Catalog or the SSISDB Database ?
Which verison of SQL Server do you run ? Do you have an error message when you try to create a new catalog ?
Check if :
English is not my native language... so, you know... sorry in advance 😉
March 16, 2023 at 2:30 pm
Yes of course.
SQL 2019.
No error.
They are gone but new catalog NOT available to select and use. The only way is to restart the service!
August 2, 2023 at 2:15 am
This was removed by the editor as SPAM
November 6, 2024 at 7:36 am
This was removed by the editor as SPAM
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply