dineshasanka - tx for your help. I need to know based on your suggestion something specific. How/where would I put the query in the script task? Would this be part of the design script, and therefore this is vb? Sorry for my juniorism in this (sql_jr)

Another option would be to use variables to hold the database and server names, and use this in the connection manager. Then, your query would just be "select * from dbo.Table"
You use a table to hold the meta data, which would allow you to dynamically loop through all your servers & databases that you want to and run the specified query.
To do this:

create two variables: strDatabaseName & strServerName

create a connection using the connection manager, using any one of your servers and databases just to set it up

Go to the properties of this connection, expand the "expressions" section and click the "build" button (3 dots)

You will then be presented with a number of properties that can have variables assigned to them. Choose ServerName from the list of properties, then click the "build" button in the "expressions" box. This opens a new window called "Expression Builder".

Expand the list of variables on the left, find the variable called "User::strServerName". Drag this down to the Expression window. You should see the following text "@[User::strServerName]". Click OK.

Do the same for the InitialCatalog property using the strDatabaseName variable

That's it. You can now change these variables either dynamically using a meta data loop, or at run time, or on an ad-hoc basis.
I think that is a little simpler than using script tasks to build dynamic sql, plus it works across any tasks that use that connection. Allows for easier maintainance and reduces the need for hard coding.