Connection Managers and Aliases
at work, use instance of sql server named workserver\sql.
at home, run local instance of sql server called homeserver.
i use visual studio database projects quite heavily in conjunction ssis projects, there kinds of references workserver\sql in solutions/projects.
on home workstation, if create alias called workserver\sql "points" homeserver, can use various tools make sql connections without error. includes visual studio (database projects), ssms, , red-gate tools. expected.
ssis appears exception. my packages have connection managers reference workserver\sql , when @ properties of connection manager , click test connection, test succeeds, reference workserver\sql on home workstation.
when run package in vs, times-out , following error generated:
an ole db record available. source: "microsoft sql native client" hresult: 0x80004005 description: "sql network interfaces: error locating server/instance specified [xffffffff].
i know configurations preferred method of making packages portable, not question. i want know how ssis resolves aliases.
thanks all.
aliases specific bitness. if have 64-bit server, design time bids/visual studio 32-bit, runtime dtexec.exe , dtsdebughost.exe 64-bit.
you can control using property run64bitruntime in solution properties. screenshot @ http://dougbert.com/blogs/dougbert/archive/2009/03/16/debug-your-package-in-32-bit-or-64-bit-mode.aspx
both 32-bit , 64-bit aliases can set via sql server configuration manager in start menu.
thanks, jason
didn't enough here? submit case microsoft customer support team deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance
SQL Server > SQL Server Integration Services
Comments
Post a Comment