Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Specifications SMS 2003
- Thread starter wdk
- Start date
This is REALLY HARD to say. I'm going to be curious as to what Microsoft announces because SMS 2003 is so modular.
Here's an example:
If you put every server 'role'/'responsibility' on the same physical server, and this means the SQL Database, SMS Site Server, Reporting Point + IIS, Distribution Server, Management Point, Service Locator Point, Client Access Point, and Active Directory Domain Controller role:
...You could probably handle things with a 1 Ghz Processor and 512MB RAM for about 50-100 workstations distributing about 10 packages a week total, doing and inventory sweep 5 times a week.
Moving responsibilities out (like the Distribution Point or the Reporting Point) to other machines like a File Server will enhance performance and scalability. Moving the SQL Server off the machine though won't help you because interprocess communications between the SMS Server and the SQL Server are FAST compared to communicating over a LAN connection between two separate physical servers.
As you scale up past 1000 clients you'll DEFINITELY want to have the ancillary roles on servers other than the Site Server but the BIG BIG BIG mitigating factor will be how many drive spindles you have and what kind of access times your SMS services can get. Every service will want disk access time, so separating things out amongst drive spindles (and if you can, SCSI channels) is a really good idea. Of course you're going to want to have those drives be RAID5 redundant or at least RAID1 Mirrored so, you may be talking about making a bigger investment in physical drives, rather than drive capacities. (But storage is cheap so who cares?)
And by the way, double up on RAM and add a processor.
Hope that helps.
Here's an example:
If you put every server 'role'/'responsibility' on the same physical server, and this means the SQL Database, SMS Site Server, Reporting Point + IIS, Distribution Server, Management Point, Service Locator Point, Client Access Point, and Active Directory Domain Controller role:
...You could probably handle things with a 1 Ghz Processor and 512MB RAM for about 50-100 workstations distributing about 10 packages a week total, doing and inventory sweep 5 times a week.
Moving responsibilities out (like the Distribution Point or the Reporting Point) to other machines like a File Server will enhance performance and scalability. Moving the SQL Server off the machine though won't help you because interprocess communications between the SMS Server and the SQL Server are FAST compared to communicating over a LAN connection between two separate physical servers.
As you scale up past 1000 clients you'll DEFINITELY want to have the ancillary roles on servers other than the Site Server but the BIG BIG BIG mitigating factor will be how many drive spindles you have and what kind of access times your SMS services can get. Every service will want disk access time, so separating things out amongst drive spindles (and if you can, SCSI channels) is a really good idea. Of course you're going to want to have those drives be RAID5 redundant or at least RAID1 Mirrored so, you may be talking about making a bigger investment in physical drives, rather than drive capacities. (But storage is cheap so who cares?)
And by the way, double up on RAM and add a processor.
Hope that helps.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question