InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 05:18:08 GMT20http://www.sqlservercentral.com/Forums/Topic980814-359-1.aspxIf the service account that SSIS uses on the machine does not have a login on the named instance or NTFS file permissions to the data/log files of the named instance then you will be okay.Sun, 05 Sep 2010 16:21:22 GMTJoie Andrewhttp://www.sqlservercentral.com/Forums/Topic980814-359-1.aspxIntegration Services not being instance aware means you can't install multiple instances. It doesn't mean that security is compromised. SSIS still needs an account to connect to the named instance.Sun, 05 Sep 2010 12:39:18 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic980814-359-1.aspxHello,Please help me with my question. We have a senstative databases on one server and need to install a seperate named instance for helpdesk database. The existing instance and the integration services uses the same service account. The named instance will have its own service account plus the application will control the logins and user id's for this named instance. My question ; is it safe to put this named instance on the same sensative databases since the integration service account is not instance aware. Please advise the pros and cons to have this named instance where the application will control the logins and user id's where the application will create the system admin credential id's as well.Sun, 05 Sep 2010 12:33:10 GMThydbadrose