Does anyone have a feel for the pros/cons of running SSIS on it's own server vs on the same machice with your data warehouse
We have a very large number of VB routines, DTS packages and SP's that parse and load daily sales data from 3000 stores to our primary data warehouse, which is running on a fairly beefy box connected to a SAN. This data gets pushed to other SQL boxes for end user access.
Due to the complexity of the current environment, plus the load on the machine during peak processing times, We are looking at purchasing a dedicated server for SSIS to run on and moving all the "crunching" off of the SQL box. Theoretically, this would lighten the load on the data warehouse box so that it's resources would be dedicated to managing the data. This would also allow us to migrate the existing DTS work to the new environment in a controlled manner.
Thoughts anyone
Thanks, mike
SSIS on it's own server vs. running on same server with SQL.
Hot Topic
- Size specified for a binding was too small, resulting in one or more
- error 18452, Login failed for user Reason: Not associated with a trusted SQL Server connection.
- Why is the ReportControl class internal?
- Query not producing correct results and Group By Error
- Row delimiter {LF} is ignored?
- SQL Express Restore and Backup Question
- Setting DTS DataType on added column: codepage.
- STATISTICS IO: Scan Count vs Logical reads
- Escape a SQL string programmatically?
- Authentication Extension - Permissions
SQL Server
- How can I setup source connections with Sybase as Source database
- Getting DataType of a IDTSCustomProperty90 object
- Use Webservice to write user access into RS directly?
- Does the Report Manager use the RS WebService?
- Money read as DT_NUMERIC
- several queries in a dataset
- How can I assign a value to a textbox programmatically in a report?
- Hidden objects causes additional pages in pdf
- Need to copy one table into another using DTS
- DDL of an existing cube
SSIS on it's own server vs. running on same server with SQL.