Is it hard for a server with 500 Ram, to host 30 000 websites + 30000 databases, with 3 users on each a day?
Thats for Windows Server 2008, IIS7
Is it hard for a server with 500 Ram, to host 30 000 websites + 30000 databases, with 3 users on each a day?
Thats for Windows Server 2008, IIS7
Well, if you seriously limit the amount of RAM given to each database, as well as to each website, then sure, you can do it.
You do need to test it and examine the performance hit you're going to get.
500MB RAM will not be enough. You'll need a couple orders of magnitude more than that.
The exact specs you'll need depend on the workload. How many daily hits are you expecting? Are these static pages or web apps? What is considered acceptable performance? What sort of IOPS does this require? How large are the databases?
What are you really asking? And why? Are you thinking of migrating from managed servers to your own infrastructure? Are they currently running on a couple dozen servers and you're looking to save money?
Edit
The simple answer is: don't do it. Even if it works, it won't work well.
You commented that this was for a dev test machine. What will they be testing? How important is this testing? Until you provide some more detailed answers, you're only going to get more questions.
Yes. It's hard for a server to do that. Without more details, that's the best answer you can get. A more nuanced answer would be "it depends", but I'm going to say that in general, the answer is Yes.
That gets you 6kb of RAM per database, assuming that you give 200Mb for the DB and 200Mb for web server, and 100Mb for the underlying OS.
Short answer: No.
For theoretical limits on large numbers of servers see: IIS7 theoretical limits
Otherwise, 500Gb might be more realistic.