Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » SQL Server 2005 » SQL Server 2005 Integration Services » Possible to determine the datetime range of...
Add to briefcase
18 posts, Page 1 of 2
12»»

Possible to determine the datetime range of loaded data to staging table? Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
10e5x
Posted Wednesday, December 26, 2012 8:37 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, February 02, 2013 11:09 AM
Points: 97, Visits: 180
Hi all,

I have created a SSIS package. In the control flow i have a Execute SQL task which will truncate my staging table and followed by a Data Flow task that loads the source data to my destination staging table. Currently, my Data Flow consist of only a OLE DB Source and a OLE DB destination. However i would like to define the life range of data in my staging table but i do not know how to achieve that. Meaning i will only extract a specified range of data from source and load it into the staging table. In my source, there are two varchar fields EVENT_D and EVENT_T. So for example, if i run my package at 26/12/12 11:00:00, Data to be extracted and load into staging are data with EVENT_D + EVENT_T between 23/12/12 07:00:00 to 26/12/12 08:00:00

and if i run my package at 27/12/12 14:00:00 my loaded data will be between:
27 Dec 0800 - 73 hours TO 27 Dec 0800.

and if i run my package at 27/12/12 07:59:00(which is v rare) my loaded data will be between:
23/12/12 07:00:00 to 26/12/12 08:00:00

Is this achievable? I guess one of the problem would be my two varchar field and it is in the format of DD/MM/YYYY hh:mm:ss

Thanks,
10e5x
Post #1400438
SatishAyyar
Posted Wednesday, December 26, 2012 9:37 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, June 17, 2013 10:06 PM
Points: 479, Visits: 410
You may use a conditional split transformation in the Data flow tab. You can write any number of conditions in this transformation and each condition have a respective output. So which ever condition is satisfied that specific data can be directed to the next step as you want.

You can also use functions to change the datatype of your columns as per your need
Post #1400442
Phil Parkin
Posted Thursday, December 27, 2012 1:53 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:39 AM
Points: 4,328, Visits: 9,667
Depending on the nature of your OLEDB source (is it an RDBMS?), the most efficient way would be to CAST the varchar date/time columns to a single column with a datetime datatype and use a select query with an appropriate WHERE clause to provide the data (and not just the whole table).

An even better way would be to add a proper datetime column to the source data, but I'm assuming that's not allowed? If there's a lot of data in this table and it's growing, any method is going to gradually grind to a halt, unless you are somehow able to get a useful index on it (eg, in SQL Server, on a computed datetime column added to the base table).

____________________________________________________________________________________________

Help us to help you. For better, quicker and more focused answers to your questions, consider following the advice in this link:

http://www.sqlservercentral.com/articles/Best+Practices/61537/

If you are asking for help and your post does not contain a question, you should expect responses which do not contain any answers. Put a question mark in there somewhere - it's not rocket science.
Post #1400495
10e5x
Posted Thursday, December 27, 2012 2:09 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, February 02, 2013 11:09 AM
Points: 97, Visits: 180
Hi Phil,
Once again thanks for replying and helping. Ya my source it is from RDBMS. Your suggestions are too complicated to me. I am trying some other simpler way. Maybe two new derive column of EVENT_D and EVENT_T as datetime first then use conditional split. Btw are u able to help me with the expression?
Post #1400500
Phil Parkin
Posted Thursday, December 27, 2012 2:18 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:39 AM
Points: 4,328, Visits: 9,667
Is the source a SQL Server database?

____________________________________________________________________________________________

Help us to help you. For better, quicker and more focused answers to your questions, consider following the advice in this link:

http://www.sqlservercentral.com/articles/Best+Practices/61537/

If you are asking for help and your post does not contain a question, you should expect responses which do not contain any answers. Put a question mark in there somewhere - it's not rocket science.
Post #1400501
10e5x
Posted Thursday, December 27, 2012 2:48 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, February 02, 2013 11:09 AM
Points: 97, Visits: 180
Its Oracle View
Post #1400518
Phil Parkin
Posted Thursday, December 27, 2012 2:54 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:39 AM
Points: 4,328, Visits: 9,667
OK, then you need help from an Oracle developer to design your SELECT statement for the OLEDB source.

Select col1, col2
from table
where [convert varchar date and time to datetime] between [startdate] and [enddate]

The problem with trying to do this all in SSIS is that you will always have to process all of the rows in the source table. If the source table is growing, as I mentioned before, your process will get slower and slower.

____________________________________________________________________________________________

Help us to help you. For better, quicker and more focused answers to your questions, consider following the advice in this link:

http://www.sqlservercentral.com/articles/Best+Practices/61537/

If you are asking for help and your post does not contain a question, you should expect responses which do not contain any answers. Put a question mark in there somewhere - it's not rocket science.
Post #1400524
10e5x
Posted Thursday, December 27, 2012 3:06 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, February 02, 2013 11:09 AM
Points: 97, Visits: 180
You are right, definately will have overhead. i try to get it done first before looking at efficiency issue. Actually my problem is defining startDate and endDate. Thanks phil
Post #1400530
Phil Parkin
Posted Thursday, December 27, 2012 4:12 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:39 AM
Points: 4,328, Visits: 9,667
10e5x (12/27/2012)
You are right, definately will have overhead. i try to get it done first before looking at efficiency issue. Actually my problem is defining startDate and endDate. Thanks phil


OK, I've looked at your original post again. I'm not sure I understand the logic for setting the start and end dates - can you explain it?

____________________________________________________________________________________________

Help us to help you. For better, quicker and more focused answers to your questions, consider following the advice in this link:

http://www.sqlservercentral.com/articles/Best+Practices/61537/

If you are asking for help and your post does not contain a question, you should expect responses which do not contain any answers. Put a question mark in there somewhere - it's not rocket science.
Post #1400548
10e5x
Posted Thursday, December 27, 2012 8:14 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Saturday, February 02, 2013 11:09 AM
Points: 97, Visits: 180
Phil Parkin (12/27/2012)
10e5x (12/27/2012)
You are right, definately will have overhead. i try to get it done first before looking at efficiency issue. Actually my problem is defining startDate and endDate. Thanks phil


OK, I've looked at your original post again. I'm not sure I understand the logic for setting the start and end dates - can you explain it?


The start date will always be 73 hours before the end date. While the end date will be the nearest 8am but its definitely a datetime of a past. E.g:
Datetime when package run: 24/12/12 0900
Startdate: 21/12/12 0700
Enddate: 24/12/12 0800

Datetime when package run: 25/12/12 2300
Startdate: 22/12/12 0700
Enddate: 25/12/12 0800

Datetime when package run: 26/12/12 0759
Startdate: 22/12/12 0700
Enddate: 25/12/12 0800

Datetime when package run: 26/12/12 0800
Startdate: 22/12/12 0700
Enddate: 25/12/12 0800

Datetime when package run: 26/12/12 0805
Startdate: 23/12/12 0700
Enddate: 26/12/12 0800

As u can see i want the data to be included from my soure to my staging span accross 73hrs. I want 73hrs worth of event data. So EVENT_D + EVENT_T should be between the Startdate and Enddate

Thanks in Advance,
10e5x
Post #1400780
« Prev Topic | Next Topic »

Add to briefcase
18 posts, Page 1 of 2
12»»

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.