|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, March 22, 2013 6:04 AM
Points: 46,
Visits: 205
|
|
I have a scenario where I need to import data from a server to another one. The data transfer is expected at 700 XML files ( of maximum size 5kb each ) per hour. The data from xml file will be read by a python program which inturn calls a stored proc which transfers the file content to table. after that, the processed files will be moved to processed folder from the landing zone. I am asked to estimate the capacity of server required. Could anyone help please ?
processor, RAM, Disk memory, etc.
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:06 PM
Points: 32,930,
Visits: 26,816
|
|
SQL Kidu (9/30/2012) I have a scenario where I need to import data from a server to another one. The data transfer is expected at 700 XML files ( of maximum size 5kb each ) per hour. The data from xml file will be read by a python program which inturn calls a stored proc which transfers the file content to table. after that, the processed files will be moved to processed folder from the landing zone. I am asked to estimate the capacity of server required. Could anyone help please ?
processor, RAM, Disk memory, etc.
You're missing a couple of key pieces of information here.
1. What is your backup plan? How long must a full backup be available on disk and how often will you stream the backups to tape? This question must be answered for both the SQL Server database and the XML files at the disk level.
2. How long do you need to keep the original XML files?
3. How long do you need to keep the XML data in a table before you can begin removal of the data through an archive system?
4. Will you be shredding the XML and storing the individual shredded elements anywhere else in the database?
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, March 22, 2013 6:04 AM
Points: 46,
Visits: 205
|
|
You're missing a couple of key pieces of information here.
1. What is your backup plan? How long must a full backup be available on disk and how often will you stream the backups to tape? This question must be answered for both the SQL Server database and the XML files at the disk level. We are planning to have Mirroring. Log shipping also could be possible. XML Files will be kept in the processed folder. There is no separate backup plan for that.
2. How long do you need to keep the original XML files? May be a month
3. How long do you need to keep the XML data in a table before you can begin removal of the data through an archive system? 4 Months
4. Will you be shredding the XML and storing the individual shredded elements anywhere else in the database? No
|
|
|
|