SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-27-2008, 06:24 PM
| ||||
| ||||
 Re: NAS recommandation for dev team... Note that multiple instances *is* allowed on same license for SE when you use Per Processor licensing. Not per seat, though: http://www.microsoft.com/sql/howtobuy/faq.asp -- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Ray" <someone@nowhere.com> wrote in message news:7QC7e.3523$716.636@newssvr19.news.prodigy.com ... > One note further. We may be blurring the line between development and production here but the SQL > license for Standard does not allow for the install of multiple instances. If this will only be > for development purposes install the developer edition. Then you can use instances. > > > "Jéjé" <willgart_A_@hotmail_A_.com> wrote in message news:ewKgX8OQFHA.3628@TK2MSFTNGP15.phx.gbl... >> when I talk about "production" I talk about released version, but not a production server with >> end-users connected on it! >> so the "production" version is here for front end development & demonstrations. >> >> The real production server are deployed in our client's servers so its a complete and dedicated >> environment. >> >> Also I split the "production" and the "developpers" versions into 2 separate instances of SQL >> Server. >> >> >> "Ray" <someone@nowhere.com> wrote in message >> news:8ws7e.3396$716.2013@newssvr19.news.prodigy.co m... >>> Having Dev and Prod on the same server is a recipe for either high risk or low performance. >>> Those are your choices without spending a lot of money on a high-end system. By high risk I >>> mean there's no good way to separate the system resources or the SQL server into two distinct >>> units. The developers in this situation will bring down your production system sooner or later. >>> By low performance, you could over come most of the risk by using Virtual PC or VMware to divide >>> the computer resources into two systems. But these are generally slow performers. >>> >>> This is a case of needing to buy two servers. I assume you are using SQL Server 2000 Standard >>> Edition. Keep the server you have and buy another cheaper system for the developers. Install >>> the developer edition on it. >>> >>> Ray >>> >>> >>> "Jéjé" <willgart@BBBhotmailAAA.com> wrote in message >>> news:OA4v%23GIQFHA.1176@TK2MSFTNGP12.phx.gbl... >>>> Hi, >>>> >>>> I want to setup a computer or server as a storage server to host database files. >>>> >>>> I'm not looking for a top performance system because its for "small" datawarehouses and for >>>> development / test purpose. >>>> small = 5 to 20gb (generally a subset of data) >>>> >>>> I want to allow a developper to copy any database to test something without breaking anything >>>> on original databases. >>>> >>>> my SQL Server server will host tempdb (master & msdb) and original databases. >>>> >>>> I plan a computer like a standard PC with 4 * 80 gb SATA drives in RAID 0+1 + Gigabyte network >>>> card and switch + Win 2003 standard >>>> >>>> I know that this type of config is not safe and performance consuming , but also its a cheap >>>> solution :-) >>>> and also is development purpose, so I'll have 1 to 3 users at the same time on a database. >>>> >>>> My database server is a 2 * P4 Xeon HP server with 4Gb of RAM. >>>> >>>> what do you think about this? >>>> what other element I have to think in the config? >>>> >>>> does it better to boost local computer of each developper and install a dev edition of SQL on >>>> each one? >>>> >>>> thanks for your feedback. >>>> >>>> Jerome. >>>> >>>> >>> >>> >> >> > >      |
Linear Mode
