hi we just stood up an azure vm running 2022 developer and i see ssis is running. it is for development.
the catalog is there. so i'm expecting for it to be easy to deploy copies of prod projects/pkgs there.
but i dont see ssisdb. whats its role these days? one reason i am concerned is that whomever authored the project i'll try to stand up on the new vm put some tiny admin/metadata type tables in ssisdb . i dont know if something is going to create ssisdb automatically as i muddle thru this or if i need to create it myself using the prod db as a model.
August 21, 2024 at 3:54 pm
When you say 'the catalog is there', what do you mean? SSISDB is the catalogue. The action of creating the catalog creates SSISDB.
August 21, 2024 at 5:41 pm
thx phil. "integration services catalog" under management but with nothing in it.
so stupid me went and created a db called ssisdb.
i think i need to remove that and let "add a catalog" (rt click on integration services catalog) create that db? never did this before.
Yes, that's the way.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply