Hi,
This is probably more of a Windows question, but I think I would get a better answer here.
We have 10 reports running from our test environment (SQL Server 2k) that should be triggered by an event file that the SQL sever creates, this is how it works on our live system (where there are many more reports running)
The SQL job deletes the previously created file, performs the ETL then creates a new file to run the reports. The problem is, the file created has the same creation date as the one that was deleted, just the modify date changes and so the reports don't run.
This does not happen on our live system, perhaps because the ETL process is a lot longer? Has anyone else had this, and if so, did you fix it?
Thanks
mrees
This is probably more of a Windows question, but I think I would get a better answer here.
We have 10 reports running from our test environment (SQL Server 2k) that should be triggered by an event file that the SQL sever creates, this is how it works on our live system (where there are many more reports running)
The SQL job deletes the previously created file, performs the ETL then creates a new file to run the reports. The problem is, the file created has the same creation date as the one that was deleted, just the modify date changes and so the reports don't run.
This does not happen on our live system, perhaps because the ETL process is a lot longer? Has anyone else had this, and if so, did you fix it?
Thanks
mrees
