microsoft / microsoft/sqlmanagementobjects
Enable Int value for JobSchedule.ActiveStartTimeOfDay and JobSchedule.ActiveEndTimeOfDay properties
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 143
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Currently JobSchedule.ActiveStartTimeOfDay and JobSchedule.ActiveEndTimeOfDay properties only accepts TimeSpan value, so it requires to perform some additional steps to convert a given time value to timespan. SQL Server already has all the validation steps to check if a given active_start_time (int, default of 000000, which indicates 12:00:00 A.M. on a 24-hour clock, and must be entered using the form HHMMSS) or active_end_time (int, default of 235959, which indicates 11:59:59 P.M. on a 24-hour clock, and must be entered using the form HHMMSS) is valid.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the JobSchedule.ActiveStartTimeOfDay and ActiveEndTimeOfDay property definitions and the related SQL Server scripting or validation entry points. Compare the current TimeSpan handling with SQL Server's active_start_time and active_end_time integer format, then identify the existing tests for JobSchedule. Done means valid HHMMSS integer values are accepted for both properties and invalid values remain rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100