Need a named instance to act as a default instance

  • 6 months into a migration project, the vendor MAS500 informed me a module we what to use, DIM which publishes jobs to SSIS will only work on the default instance.

    I changed my named instance IP port to 1433 and changed the line in msdstsrv.ini.xml to

    ., when accessing the catalogs in SSIS i recieve an error the sql server is not present or not available.

    what is / how does SSIS connect to the default instance. I would like to fool it into thinking my named instance is a default instance.

  • SSIS doesnt' connect to anything. The packages have connection strings. You can possibly set up an alias and aim it for 1433, or an FQDN in DNS and then point it there.

  • should the alias be mssqlserver pointing to the named instance?

  • Are they saying they have a hard coded connection string? I'd ream the vendor if this is the case.

    The alias could be anything. You give it a name and then point it to a port and server. The server would be your named instance.

    If you have a default instance, be sure you've changed it's port, or shut it down.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply