I am planning to implement the consolidated messaging hosting platform 3.5. As you can find in the suggested configuration on the MS website, there is a SQL server running in the backend. It will be used for database hosting, as well as for sharepoint backend
and provisioning. We do not except a very high number of database users.
I was looking at the SPLA price list and note that a SQL 2000 workgroup edition has a nice CPU pricing compared with the standard edition. Do you think that it is wise to implement the SQL workgroup edition 2000 i.o. the SQL standard edition 2000?
What would be the real limitations compared with the standard edition? Will my customers note any difference? Is the CPU license enough for all db's (provisioning, sharepoint, db hosting), or do I need extra SALs?
Can I use an unauthenicated processor license as long as my customers buy a webhosting or sharepoint package in combination with db hosting? (read: they will be connected on the front end and are only able to access the db's via this frontend)
WimVM
Member
736 Points
238 Posts
SQL 2000 hosting question in the consolidated messaging platform 3.5
Sep 26, 2006 05:41 AM|LINK
Hello,
I am planning to implement the consolidated messaging hosting platform 3.5. As you can find in the suggested configuration on the MS website, there is a SQL server running in the backend. It will be used for database hosting, as well as for sharepoint backend and provisioning. We do not except a very high number of database users.
I was looking at the SPLA price list and note that a SQL 2000 workgroup edition has a nice CPU pricing compared with the standard edition. Do you think that it is wise to implement the SQL workgroup edition 2000 i.o. the SQL standard edition 2000?
What would be the real limitations compared with the standard edition? Will my customers note any difference? Is the CPU license enough for all db's (provisioning, sharepoint, db hosting), or do I need extra SALs?
Can I use an unauthenicated processor license as long as my customers buy a webhosting or sharepoint package in combination with db hosting? (read: they will be connected on the front end and are only able to access the db's via this frontend)
Thanks