Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Unable to access SQL Server instance alias as connection manager


Unable to access SQL Server instance alias as connection manager

Author
Message
rwitt 95744
rwitt 95744
Grasshopper
Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)

Group: General Forum Members
Points: 23 Visits: 149
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
rwitt 95744
rwitt 95744
Grasshopper
Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)

Group: General Forum Members
Points: 23 Visits: 149
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
Phil Parkin
Phil Parkin
SSCrazy Eights
SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)SSCrazy Eights (8.4K reputation)

Group: General Forum Members
Points: 8383 Visits: 19502
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.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
rwitt 95744
rwitt 95744
Grasshopper
Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)

Group: General Forum Members
Points: 23 Visits: 149
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search