cluster shutdown

I have a Compaq DL380 G2 package cluster.
Prior to the Hurricane (scare) for the Houston area, all servers and the
cluster were shutdown/powered down.
I am looking for the proper shutdown/powerup procedure for the cluster.
We had a hard time getting the cluster to be recognized by the server.
Make sure your Domain Controllers and network switches are up and running
before powering up the cluster. The disk array starts first, then one host
node. Take all resource roups except the quorum group offline after the
first node is up. Bring up the second node only after the first node is
operational . Make sure the disk resources and IP addresses shift
correctly, then bring the resource groups online on the corret hosts.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Harold Clemons" <harold@.hal-pc.org> wrote in message
news:OqVZe.32210$S26.11108@.tornado.texas.rr.com...
>I have a Compaq DL380 G2 package cluster.
> Prior to the Hurricane (scare) for the Houston area, all servers and the
> cluster were shutdown/powered down.
> I am looking for the proper shutdown/powerup procedure for the cluster.
> We had a hard time getting the cluster to be recognized by the server.
>

Closing a Child Package After it Runs

Hello,

I have a package which runs several child packages. All works well and everything runs, but when it runs each of the children packages, it opens it, runs it and then it stays open. When the whole thing is done, there are about 25 or so open packages. Should they close after they run? Is there a setting I need to do this?

The point I am in SSIS is that I have gotten a decent feel for creating packages, but everything is still in debug mode. I need to take the next step to learn how to have this stuff run automatically or from a procedure outside the SSIS interface. Does that make any sense? If so, where can I learn about that.

Thanks for the help.

-Gumbatman

When you say the package remains open after execution, you are talking about the package designer window on Visual Studio (BIDS)? If so then don't worry it us not an issue.

When you execute a package in the designer it actually has an entirely different instance loaded for the execution. The debugger uses a special application, dtsdebughost.exe, to host the running package. This then hooks into the designer to give you progress information, colours and other messages.

The real execution package has closed you just see the static designer artefact, the open package window. Compare this with execution without debugging, (try Ctrl+F5 is it inside VS) which uses DTExec, a regular execution host.

|||

DarrenSQLIS,

Thanks so much for the information. I didn't know about (or understand) that when running it in the BIDS.

-Gumbatman

CLONING PACKAGES

I loved the DTS feature that allowed saving DTS package as a VB model. With a bit of coding you could generate a number of packages from one template.

Are there any analogous solutions for SSIS? I cannot find anything.

My goal is simple. I have an ETL step that transfers data from staging dimension table to the corresponding star schema table in the subject matter database. I have two types of packages for SCD type 1 and type 2. Do you have any suggestions on how I can clone packages so that I don’t have to go manually through each of them to replace certain items such as stored procedure names, etc.

Thank you!

Besides copying the .dtsx file and editing the copy to suit your needs?|||You can create a program to generate SSIS packages. If you want to reverse your current packages into C# code, take a look at http://www.ivolva.com/ssis_code_generator.html.|||You could also create a template for each type of load process and store them in the \Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems folder. I think that's the correct place.|||Phil Brammer: Yes, I want to be able to change all hard-coded string dynamically. Assuming I use standard naming convention all object names will have the same structure. All I want to do is loop through table names and replace appropriate strings within the existing template package to generate new packages on the fly.|||jwelch, that's an interesting solution. I'll try to play with you and let you know if it works. But it seems it's what I need.|||

LoveDanger wrote:

Phil Brammer: Yes, I want to be able to change all hard-coded string dynamically. Assuming I use standard naming convention all object names will have the same structure. All I want to do is loop through table names and replace appropriate strings within the existing template package to generate new packages on the fly.

Using expressions, you can build just ONE package to do this though.

Provided the structures of all of the tables (both sources and destinations) are all the same... That is, you can dynamically adjust the tables the OLE DB sources and destinations go against.|||Thanks Phil, this should work. I assume the transformation part would be tricky (I'm not sure how to map all the columns dynamically), but I'll check if that could be done. Also, I believe the solution posted by jwelch (http://www.ivolva.com/ssis_code_generator.html) should work if one still wants to generate numerous packages.

Thank you all!
|||Note: My solution works if you are looping through tables that have the same structure. If they don't, then my solution won't work. Once you build the package (mappings and all) you can start using expressions to dynamically change the table names.|||Yeah, in my case we have different set of attributes for each dimension that I'm not sure how to handle. I used your approach with BCP though - use only one package to transfer data from a number of flat files to SQL Server tables. Though you still have to generate format files for each that pretty much translates your column mappings.|||

LoveDanger wrote:

I loved the DTS feature that allowed saving DTS package as a VB model. With a bit of coding you could generate a number of packages from one template.

Are there any analogous solutions for SSIS? I cannot find anything.

My goal is simple. I have an ETL step that transfers data from staging dimension table to the corresponding star schema table in the subject matter database. I have two types of packages for SCD type 1 and type 2. Do you have any suggestions on how I can clone packages so that I don’t have to go manually through each of them to replace certain items such as stored procedure names, etc.

Thank you!

Sounds to me like you want to use templates. Matt explained where to drop them elsewhere in this thread.

-Jamie

|||

Well, I am not really sure how would templates solve my problem. I will still have to go through each package task and replace the names of the objects manually.

Does template allow you to do search and replace for the entire package?

|||

LoveDanger wrote:

Well, I am not really sure how would templates solve my problem. I will still have to go through each package task and replace the names of the objects manually.

It sounds as though you'll have to do that regardless of the solution though?

LoveDanger wrote:

Does template allow you to do search and replace for the entire package?

No, not really. You could open up the package's XML (right-click on the package and select 'View Code') and do a Find-Replace that way of that's what you want to do.

-Jamie

|||Thanks Jamie, I think this would be the easiest in my case. At least it will save time on going through each task manually.

Anastasia|||

LoveDanger wrote:

Thanks Jamie, I think this would be the easiest in my case. At least it will save time on going through each task manually.

Anastasia

Cool. Take a copy of the package before you alter it

Client Tools for SQL Server

Where exactly does one find the installation package for Client Tools for SQL
Server. SQL Server 2003 running on a Win2003 server. Workstations now
need console, etc. ODBC links from the workstation to the server work fine.
Thanks.
Not sure what you mean by installation package - are you
trying to install just the client tools or are you looking
for sqlredis which installs the client components? sqlredis
is the distribution executable that installs the client
components (not client tools). There is info on this in
books online. But it sounds like you want to install the
client tools such as Enterprise Manager, Query Analyzer,
etc. You can use the SQL Server installation CD. Refer to
the topic in books online:
How to install client tools only (Setup)
-Sue
On Mon, 28 Mar 2005 14:49:03 -0800, "Gene"
<justasking@.newsql.user.com> wrote:

>Where exactly does one find the installation package for Client Tools for SQL
>Server. SQL Server 2003 running on a Win2003 server. Workstations now
>need console, etc. ODBC links from the workstation to the server work fine.
>Thanks.