InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 10:54:48 GMT20http://www.sqlservercentral.com/Forums/Topic723554-146-1.aspx[quote][b]sunny Brook (5/26/2009)[/b][hr]Type in[b] Holiday Table[/b] in the upper right [b][size="3"]Search[/size][/b] area on this page, and hit [b]Go[/b]. You would get a lot hits.[/quote]Thanks, amazing that adding table to holiday gives such better results :-D.Tue, 26 May 2009 15:37:26 GMTJoshua Austill-492084http://www.sqlservercentral.com/Forums/Topic723554-146-1.aspxCalendar table with holidays in it is definitely the way to go. The biggest consideration with that is having someone keep the holidays up-to-date, or you end up with a sort of Y2K issue.You can have it auto-populate the standard ones. But if there are business-specific holidays, or if a new federal holiday is created, there needs to be a well-documented means of handling those. In many companies, HR issues a list of the year's holidays at the end of the prior year, so it can be handled by them, and they can use it to issue the list if you set that up. That works pretty well.Tue, 26 May 2009 14:07:32 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic723554-146-1.aspx[quote][b]Andy Hogg (5/26/2009)[/b][hr]I believe that your thinking with a holiday dates table is spot on Joshua.Your job could simply determine if today's date is in the table, and if not, could then run another separate job using sp_start_job to perform the actual import.[/quote]Ya, I hadn't even thought of just using sp_start_job, that actually makes this seem like a fairly trivial task. Thanks!Tue, 26 May 2009 13:45:13 GMTJoshua Austill-492084http://www.sqlservercentral.com/Forums/Topic723554-146-1.aspxType in[b] Holiday Table[/b] in the upper right [b][size="3"]Search[/size][/b] area on this page, and hit [b]Go[/b]. You would get a lot hits.Tue, 26 May 2009 13:42:54 GMTDBA in Unit 7http://www.sqlservercentral.com/Forums/Topic723554-146-1.aspxHi,Go to maintenance plan >>>edit>> Skip sat and sun for weekends.On a perticular holiday skip perticular dayTue, 26 May 2009 13:41:22 GMTPradyothana Shastryhttp://www.sqlservercentral.com/Forums/Topic723554-146-1.aspxI believe that your thinking with a holiday dates table is spot on Joshua.Your job could simply determine if today's date is in the table, and if not, could then run another separate job using sp_start_job to perform the actual import.Tue, 26 May 2009 13:38:15 GMTAndy Hogghttp://www.sqlservercentral.com/Forums/Topic723554-146-1.aspxHello all. I'm having a hard time with something. I have a job that runs Monday through Friday, and goes out to an external database and does a simple import. My problem is that on holidays this external database does not get updated, so I end up with duplicates of every record. This isn't a huge deal as I can just delete half of them based on the auto increment ID field and move on. However, it would be nice if this didn't happen at all. The data I am importing is so simple its hard to programatically know that it's duplicate data. Its basically just a list of account numbers, balances, account types, names, and an Average Balance for the month. From this its not possible to say if the account number is the same it's a duplicate, because the account numbers are always the same, only the balances change.So, I had the thought that I could populate a simple table called holidays, then have my process check that table against today's date and if there's a match skip the rest of the job. I'm not sure if I'm even going down the right path with my thinking though. Has anyone else had to work through this before?Tue, 26 May 2009 13:27:56 GMTJoshua Austill-492084