Set SSIS variable = database connection manager name

Question

Is it possible to set a SSIS string to only the name of a database connection manager or even the connection string it uses ? I don't see an option for that in Evaluate as expression property of ssis variable.
This is what I mean - 
SSIS Connection manager name = SQL_DBASE
SSIS String str_managerName = SSIS Connection manager name: Can you do this dynamically in SSIS ?

Answer 1

I'm guessing what they really want to do is evaluate some indicator (some input from a user or an infrastructure setting) and then dynamically connect to any one of 10 (arbitrary example) database servers based on what they get as input.  They
don't care about the connection manager per se.  What seems reasonable is the that the Connection Manager might take a server variable but if they wanted to do things like that they would have bought Datastage.
You might try attacking this problem at the Control Level and then connect to the database you want based on a variable you set.   I'm seeing that a Sequence Container can branch on the contents of a variable. 
Or if the dba is your friend you might get the dba to add all your servers as linked servers to a central connection machine and then you might be able to do this by putting the ssis variable in a "Sql Command from a Variable" variable. 
It might look something like this:
Server is designated in ssis var @[User::Machine]
then executing from a variable
"select top 100 * from " + @[User::Machine] + ".mydb.dbo.mytable"
Be careful as hades about levels of indirection and what quotes you want at what level.  Evaluate Expression in ssis helps with this.  The syntax I show works only with an ms sql connection server to a remote ms sql server.  This is what a
dynamic connection to a linked server connection to Oracle would look like:
"select * from
openquery("+ @[User::Machine] + ",'select * from oradb.oratable where rownum < 100')"
When ever a thousand of your best friends are helping you connect to your database (using tools like linked servers as opposed to direct connections) it's probably best to use with only small specific updates or queries, large queries or large
updates would probably take a long time and or might not finish.  But try it before you give up.   We are actually doing fairly large Oracle queries (5-10 million rows) through ms sql linked server.