February 1, 2024 at 9:12 am
Oh boy, I think you need to go and read up on how to properly handle the SSISDB.
Someone / some team has a serious learning curve, SSISDB cannot just be handled like any other database.
One cannot simply just delete the SSISDB to clean up the catalog.
Migration went wrong.
The cleanup went wrong.
What else is going to go wrong here?
To clean up the SSISDB and the catalog, you must first delete the catalog (NOT THE DATABASE), then delete the database, then delete the SSIS Maintenance Agent Job, reboot the server.
Then you can recreate a new SSIS Catalog which will create a new SSISDB and a new SSIS Maintenance job.
Instead of trying to hack this together, I suggest you get another server spun up, create the SSISDB cleanly and then migrate all your user databases again, redeploy everything again from VS, as heck knows what else you may have screwed up in relation to SSIS catalog/DB.
Time to start clean is my suggestion.
February 1, 2024 at 9:28 am
I have not deleted the SSISDB but catalog. Sorry catalog was named as SSISDB and hence the confusion.
Thanks,
Charmer
February 1, 2024 at 9:40 am
Again, I still so go and start on a clean environment, going to be your easiest option I think at this stage instead of trying to piece the information provided into what has actually happened.
Then as I mention go and read up on how to handle the SSISDB correctly.
February 1, 2024 at 9:47 am
Again, I still so go and start on a clean environment, going to be your easiest option I think at this stage instead of trying to piece the information provided into what has actually happened.
Then as I mention go and read up on how to handle the SSISDB correctly.
Will definitely and actually I am searching for it already.
But to make this clear to myself, get a new server and restore only the databases but anything related to SSISDB/catalog or agent jobs. Then create a catalog and so on. That's what you say is the best approach?
Thanks,
Charmer
New server
Restore all your user databases - Don't do anything with SSISDB, do not backup and restore this, this is what got you into this mess in the first place.
Create a new catalog, which will create a new SSISDB
Remember the encryption pass phrase you use.
Redeploy everything from Visual Studio into the new fresh clean SSISDB catalog.
Backup the SSISDB master key
Store that key in your backup vault
Save the pass phrase in your secrets / key vaults
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply