DTS | Forum profile

Ah, OK. Think I got it now. (since your op title reference 2005, I'll assume you will be using SSIS. If not, this won't be much help, just so you know.) You could possibly trim your table down to two DateTime fields, which would make this a little easier to manage: CREATE TABLE dbo.PackageControl ( StartPoint DATETIME NOT NULL, EndPoint DATETIME NOT NULL) Create 2 package variables of Date datatype (it is actually DateTime data type,...

I have SQL 2005 and 2008 on the same box.  Can I install 2005 and 2008 Integration Services on the same box also? I currently have 2008 Integration Services installed. Or can anyone point me to directions on how to set up permissions that will allow a 2005 Job to interact with 2008 SSIS package? Thanks in advance

Todd, I bow to the master.  I didn't burn a MSDN incident, Microsoft Support addressed my issue for free.  Here is their response which is a longer version of your response. The quote below is from Microsoft Support replying to my email stating that changing from a SQLDB data destination to an OLEDB destination worked. "Yes, according to the defect description, OLE DB should work, the warning only says that the...

For comparison test, I splited out txt file for 14 files and used Access to import all 14 files into SQL. Total row count are the same: 5276944 but there is big difference in data space. Below is the list: Using Access: 3,793,609 MB Using SQL: 8,184,969 MB I do not know why.

For anyone who has similar problems, the solution is found in MSDN article: Integration Services Considerations on 64-bit Computers http://msdn.microsoft.com/en-us/library/ms141766(SQL.90).aspx Signature Van T. Dinh > SQL Server has been updated to SP3 (Build 9.00.4035) but the results of > the repeated tests are exactly the same as previous post. > > Any idea? > > Thanks & cheers

Thank you very much Todd - I will go ahead & try to implement - thanks for your quick response! best regards, James > Hello James and welcome to the SSIS(DTS) forums. > [quoted text clipped - 45 lines] > > thanks, > > James

The purpose of this DTS is to extract data from mysql into sqlserver, then do some manipulation and email the result, every hour based on the start and end time. Example: date_column, start_time, end_time 12/8/2009,8am,11pm 12/9/2009,10am, 10pm 12/10/2009,9am, 10pm etc.. Based on above sample, say tomorrow (12/8) the dts will run starting at 8am, every hour until 11pm. Hope this is clear. > You'll need to be more specific. You want...

Craig, EXEC sp_start_job only gives the command to start the job, so the trigger will end once the job is started.  The job itself runs asynchronously from the trigger in another process. RLF > Thanks very mich guys. > [quoted text clipped - 13 lines] > Thanks guys. > .

Thanks very mich guys. Todd, I am looking at that SSSB thing. I have never used it, but I have google. :) That's for warning me about that issue. So, the trigger would basically be 'stuck' with the SSIS package fires? Not good. Thanks. My mistake as well - we're using SQL Server 2005, and SSIS. I keep forgetting that the name is different. I have updated my documentation to reflect that. Thanks again. Russell, thanks! My...

Hi Maeda, For debugging and error handling in SSIS, you can refer to the following articles: Troubleshooting Concepts (Integration Services) http://msdn.microsoft.com/en-us/library/ms138039.aspx Chapter 5: Debugging and Error Handling with SSIS Packages http://technet.microsoft.com/en-us/library/cc304419.aspx Best regards, Charles Wang