DSXchange

You need to ask your DBA how they would check to see if an index is enabled or not. I am sure they have stored procedures for this. You need some way to call this procedure and get an answer as to yes or no they are enabled.

By the way Ken's stuff is always professional, productionalized and well documented. My free stuff is not always documented and often one off jobs so they never get productionalized. I just want to point you in the right direction and not neccessarily give you the total solution. The total solution ...

You are welcome.

You are welcome.

Ken

Can we still download these off your web site?

Sure you can do this but usually we create stored procedures to do this. I prefer functions that return 1 or 0. Then you select MyFunction('tablename') from dual; then write it to a hashed file. If it is a 1 then good else bad. Call a DS routine to see what this value is.

They are talking about SQL Server partitioning where you break one table up into to many tables but they still act as one. You usually want to break a table by either a reporting field or a date field or both. Some people want to partition by state or country for reporting purposes. Another way woul...

Partitioning has changed a lot in 2005. It is starting to look more like Oracle and other databases. Before that is was ugly. It is sort ugly now in the way it picks a partition. Not real flexible.

You may need to run a batch job before you run your sequences. This might be part of Ken's jobs Craig mentioned. You are probably reading the parameter values out of sequential file. This can be and should be done before a job sequence starts and not during. This is an unsupported way to load these ...

By the way Ken's batch processes are totally his invention as far as I know. I don't think he has used any code from me or anyone else. I think Craig actually uses Ken's jobs and methodolgy.

Good job. I do not like Perl. I think it is hard to read but you came up with a solution which works. Well done.

Most of us have used Universe for many years so we tend to deal with the repository tables directly with jobs or routines. This is a very clever solution. Thanks for sharing.

Do not have autosys run dsjob directly. Put it in a shell script or a batch file if on Windows.

Create a variable with the current date. Write this to a hashed file. Check this hashed file before writing to it. Make sure it is yesterday. If it is not today then run job A and write the new date to the hashed file when job A finishes.

Good point. There is not much down side. It complicates the Director listings and that is about it. I think restartability is a little more complicated but is not an issue.

Hashed files should not be considered persistent meaning these values should be recreated every job run. Select max(surrogate_key) from dimension_table -> SDKSequences This is a job included in EtlStats called reseed_sequences. The surrogate_key is a parameter and so is the table name so the SQL loo...