Pros and Cons of setting up a batch processing server?
We are converting our in-house client/server applications to be web applications using Visual Studio 2012, ASP.net, SQL Server 2014. We are starting to create some batch jobs that we would like to run without user interaction and one of my team members suggested setting up a batch processing server to handle these processes. Since this is all new to me, I was wondering if anyone could provide feedback on: the pros and cons of using a batch processing server,
is it really needed,
without it can large data files (over a gig of data) be processed without timing out if there isn't a separate server?
We are a small state agency and most of the batch processes that will be needed are annual processes with a few daily and weekly processes thrown in.
Any information you can provide is greatly appreciated.
Thank You, Ang
is it really needed,
without it can large data files (over a gig of data) be processed without timing out if there isn't a separate server?
We are a small state agency and most of the batch processes that will be needed are annual processes with a few daily and weekly processes thrown in.
Any information you can provide is greatly appreciated.
Thank You, Ang
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ste5an,
Thanks for the explanation. We don't have a data warehouse db, all the processes would run against the application dbs.
I didn't explain that we are running in a Cisco VM environment where we have a production SQL Server virtual server, a production web server virtual server and asked our network division to set up a batch processing virtual server, but they are questioning if we really need this to be a separate virtual server? I'm looking for some info to back up our desire to have it be separate. They are trying to preserve our OS licenses and we are trying to prevent performance issues.
Thanks, Ang
Thanks for the explanation. We don't have a data warehouse db, all the processes would run against the application dbs.
I didn't explain that we are running in a Cisco VM environment where we have a production SQL Server virtual server, a production web server virtual server and asked our network division to set up a batch processing virtual server, but they are questioning if we really need this to be a separate virtual server? I'm looking for some info to back up our desire to have it be separate. They are trying to preserve our OS licenses and we are trying to prevent performance issues.
Thanks, Ang
Okay, then: What kind of batch processing are we talking here about?
ASKER
ste5an,
some examples would be updating an employee's org code on various tables when they move from one org to another within the department, running a process that would purge data based on our record retention policy.
some examples would be updating an employee's org code on various tables when they move from one org to another within the department, running a process that would purge data based on our record retention policy.
How would you implement this?
Cause it sounds like a stored procedure could be sufficient. In this case you would simply use a SQL Server Agent job or a scheduled maintenance plan.
Or are we talking about SQL Server Integration Services?
Cause it sounds like a stored procedure could be sufficient. In this case you would simply use a SQL Server Agent job or a scheduled maintenance plan.
Or are we talking about SQL Server Integration Services?
ASKER
Thanks for your input, I was able to the information provided to plead my case.
Ang
Ang
ASKER
Thanks,
Ang