SQL Job or Windows Service?

  • Thread starter Thread starter Erik Cruz
  • Start date Start date
E

Erik Cruz

Hi.

The application I'm writing will need to import data from an Oracle database
to a SQL Server 2000, every 15 minutes. I am considering to create a SQL Job
or a Windows service written in VB.NET to do the task. What should I take
into account before deciding? Is there any kind of material comparing these
techniques?

TIA,
Erik Cruz
 
Hi,

Follow the steps:-

1. Create a Link server to the Oracle server
2. Create a SQL Job to read the oracle database and populate the SQL server
table.
3. Schedule the job to execute every 15 minutes.

Note:

Ensure that your SQL server agent service is running all the time.

Thanks
Hari
MCDBA
 
If the SQL server is a mission critical machine and you need to filter or process the data prior to dumping it into SQL from Oracle, I would not suggest using a job on the SQL server. I am in the same delima right now, with the already high use of the SQL server, should I add one more task to it that runs out of process of the SQL Service? SQL is auto tuning, adding other processes to it just hamper performance and adds to the administration and troubleshooting of issue. I have not been able to find a document that speaks directly to this topic. I have found a few that speaks indirectly to it, located here http://www.microsoft.com/sql/techinfo/administration/2000/default.asp. I still need ammo to build a business case using ROI

If anyone have supporting documenation on that, feel free to point it out
 
Hi Hari.

I made a simple test using a DTS package called from a job, but I didn't
create a linked server. What benefits a linked server can offer to this
task?

TIA,
Erik Cruz
 
Back
Top