Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Unable to access SQL Server instance alias as connection manager Expand / Collapse
Author
Message
Posted Tuesday, December 10, 2013 12:01 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, June 12, 2014 8:13 PM
Points: 18, Visits: 107
Greetings,
I have been handed a Visual Studio project containing about 30 ETL's. The connection managers use aliases instead of specific server names, which is good. However, when I try to set up matching SQL Server aliases on my PC, using SS Configuration Manager, I can set up the aliases, but I can't actually access them in SSIS. When I try to create a new connection manager, the aliases aren't displayed in the list, nor do the exising connection managers automatically adjust & work now that there are matching aliases (if I try "test connection" it fails.)

On my PC, SS 2008 is the default SQL Server instance. SS 2012 is a named instance, basically localhost\SQL2012. The databases required are in the localhost\SQL2012 instance. I set up (both 32 & 64 bit) aliases as:

CSDW_DWTarget - alias
tcp - connection type
localhost\SQL2012 - server

If I set up a brand-new SSIS connection manager, simply using <PC_name>\SQL2012 - not an alias - that works, but I'd prefer to set up an alias that matches the connection managers already in the project.

Thanks for any suggestions,
Randy
Post #1521629
Posted Tuesday, December 10, 2013 3:44 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, June 12, 2014 8:13 PM
Points: 18, Visits: 107
P.S. I just found that I can set up a SQL Server alias, to a named instance of SQL Server 2005 (also on my PC), and access this alias from SSIS successfully. However, I still cannot set up an alias to the SQL Server 2012 instance, for successful connections either via Mgmt Studio or SSIS.

Randy
Post #1521703
Posted Wednesday, December 11, 2013 12:28 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, July 21, 2014 11:49 PM
Points: 4,973, Visits: 11,660
You're puzzling me a bit with all this talk of aliases.

Why not just use standard connection managers and configurations / environments to control what points to what?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1521762
Posted Wednesday, December 11, 2013 7:28 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, June 12, 2014 8:13 PM
Points: 18, Visits: 107

I'm just following company standards. The typical way they've been setting up Visual Studio source-controlled projects, that have databases associated with them, is to create the database connections using aliases, so that whether the project is "live" or in development, the code is the same.

You're probably right, thought, setting up the various separate build environments would probably achieve what I need, had been having tunnel vision. I'll check into it & see what may be doable. Thanks.

I am still curious, though, why I can't set up a referenceable alias for SS 2012 but I can for SS 2005 & 2008.
Post #1521897
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse