Connecting SSIS to MSDB

Last Post 25 Feb 2009 11:27 AM by sschmid4. 2 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
sschmid4
New Member
New Member

--
23 Feb 2009 01:52 PM
I am trying to connect SSIS to an MSDB named instance that uses non-default mapping for the DATA folder. The current documentation for connecting the SSIS service to a named instance indicates that the MsDtsSrvr.ini.xml file should be altered to point to the named instance where the MSDB to be used resides. This is ok for setups that use default installation paths for the data files. However on our network we do not use the default paths for the DATA folder which holds the data files. We custom map this folder to another location outside of the named instance's Database Services. This is causing the SSIS service to not be able to map successfully to the named instance's MSDB database. Is there another setting within the MsDtsSrvr.ini.xml file that needs to be changed to account for the customized path of the MSDB database beyond the named instance setting?

sschmid4
New Member
New Member

--
24 Feb 2009 06:47 AM
There may have been confusion on my part. The Binn folder for the MSSQL.1 instance is on a drive separate from the Data, Log, and Job folders that are all located with the rest of the Named Instance folders which are mapped to the custom drive location during setup. This custom location is on a different drive than the location holding the Binn folder.

That aside, are you aware of how to direct the ini file to a custom msdb location?
sschmid4
New Member
New Member

--
25 Feb 2009 11:27 AM
We did rename the instance in the INI file and it looks to be recognizing the MSDB database now. However we had already tried this earlier in the day and whenever we tried to access the MSDB from the SSIS instance on Mgt Studio, it would timeout. We came back later in the day and were then able to access the MSDB database after all. Is there typically some latency beyond starting and stopping the SSIS service associated with this configuration change?
You are not authorized to post a reply.

Acceptable Use Policy