December 30, 2019 at 8:55 pm
Hi,
We used to be able to create SSISDB from Integration Services Catalogs within SSMS. This option has been changed that we can only create SSIS IR which is the Lift & Shift Your ETL Workload with SSIS in ADF. This option requires us to sign in and subscribe SQL Azure. We would like to keep our SSISDB on premise in the local database.
We have tried to use the older SSMS to create the SSISDB catalog. The SSISDB was catalog but when we used Visual Studio Community 2019 to push the package to the catalog, the local folder is disabled and can't store the package within the local SSISDB folder. Any suggestions?
December 31, 2019 at 9:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
January 6, 2020 at 1:59 pm
SSMS allows you to publish to an Integration Services runtime in Azure, but you can still create an on-prem SSIS catalog and deploy packages there. If you have an on-prem SQL Server, you should be able to create the catalog there. Can you share a screenshot of what you're seeing when you try to create the catalog?
Tim Mitchell, Microsoft Data Platform MVP
Data Warehouse and ETL Consultant
TimMitchell.net | @Tim_Mitchell | Tyleris.com
ETL Best Practices
January 6, 2020 at 11:41 pm
Hi Tim,
I was able to create the SSISDB now. I forgot to click the Enable CLR Integration check box on top of the screen. Everything is good.
Thanks for your reply.
Brian.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply