SDL start time is being disregarded?

[Prokein, Peter]

Folks,

When adding a dataset to the SDL a start time can be set.  If you set the start time to something other than the full hour, for example 7:05 pm, and the run time to ever hour, then it's not unreasonable to expect that the next run happens at 8:05 pm.  This is not the case, the job will run at 8:00 pm.

This is also true if you try to space out different dataset imports.  Let's say you want to import 4 datasets, each 10 minutes apart.  The set time is being disregarded and the import runs sequentially, meaning the second dataset is loaded as soon as the first one completes, regardless of whether 10 minutes have actually passed.

Is this a bug or user error?

Thanks,

Peter

--
Peter Prokein
Institute of Northern Engineering
University of Alaska Fairbanks

office: (907) 474-2720
mobile: (907) 750-0115

[Whiteaker, Timothy L]

Peter,

 

I wonder if it has something to do with the way SDL was set to run in Windows Task Scheduler?  Can you post screenshots of the schedule setups in both SDL and Task Scheduler?  Something like this:

 

SDL

 

Task Scheduler

 

 

 

Tim Whiteaker

Research Associate

The University of Texas at Austin

--
You received this message because you are subscribed to the Google Groups "CUAHSI HIS User Group Forums" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cuahsi-wds-user-gro...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Prokein, Peter]

Tim, that's exactly it!  Thanks!  It's been so long since I set that up that I totally forgot that SDL is running via the task scheduler and not as a service.

This probably also means that if I really want to actually space out the data import I will probably need to do it via SSIS rather than the SDL.

-p

--
Peter Prokein
Institute of Northern Engineering
University of Alaska Fairbanks

office: (907) 474-2720
mobile: (907) 750-0115

[Whiteaker, Timothy L]

Well, one thing you could do is set SDL to run VERY frequently in Task Scheduler.  Like every 5 minutes.  When Task Scheduler runs SDL, SDL won’t do anything unless the allotted time has passed as specified in the SDL settings.  In other words, set the timing how you want in SDL, and then make sure Task Scheduler runs SDL more frequently.

[Shahidul Islam]

We are trying to implement hydroserver in the UNIX environment. We have used hdyroserverLite to make this data available. However, the webpage loads the data and graph very slowly. It almost takes 15 minutes to download 65,000 value of single parameter  (e.g., wind speed) from a single site. Initially, we thought it was the problem with the HydroserverLite. Then we tried to access the data through hydro desktop. We  are able to download single parameter from a single site. However, it is very slow and also takes around 15 minutes to download 65,000 value of single parameter. However, if we try to download multiple parameters for the same time period, the hydro-desktop gives time-out issue. So, i am wondering we may have a issue with the wateroneflow web service which may not generate correct format of WaterML file or there may be issue with WaterML parsing.

 

here is the web service URL link:

http://w.ra-tes.org/cuahsi_1_1.php

 

Can anybody provide suggestions to solve this issue?

 

Thanks for your help.

 

Regards

Shahidul

 

 

Mohammad Shahidul Islam, Ph.D., P.E.

 

Research Assistant Professor

Department of Civil and Environmental Engineering

Clarkson University

8 Clarkson Ave.

Potsdam, New York 13699-5764

979-820-4407

sis...@clarkson.edu; sis...@bire.org