Small Scale SQL Server Deployment
-
Comments posted to this topic are about the item Small Scale SQL Server Deployment
Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices -
Great article on a subject that I hope to read more about. After all, as mentioned, the small scale setups constitute the vast majority of cases if not the most complicated ones.
-
The only thing you didn't mention (unless I missed it) is that size of the database isn't the only factor to consider. The transaction throughput is important too.
Another consideration is that most very small businesses will not have a dedicated database server. They will often have Small Business Server and run Exchange, Terminal Services, and many other services all off the same box. The hardware needs to be sized for what the server needs as a whole, not just the needs of SQL Server.
Bob
SuccessWare Software -
Nice Article. Thanks for the mention of Express and MSDE. So many small business forget these in favor of other "free" solutions using MySQL and PostgreSQL. Dont' forget that these all come with a learning curve and may cost you more in the long run.
-
MSDE / SQL Express also have a database size limit of 2GB...
But good article - nice to see comments & discussion on running smaller SQL Servers on a budget!
As for the MySQL stuff - I have to say that my last experience was with MySQL v3.5 or something and I found it to be rather awful, missing may important and basic features that I take for granted on SqlServer, such as stored procs. I too have seen several shops go with MySQL for their internal project and then decide
a) They ask us to come in and bend our software to run on MySQL - answer is always no... Some haven't wanted to run MSDE for reasons unknown
ORb) They end up throwing away everything they've done and have wasted a lot of time because they want something that MSSQL offers, or the in-house person who wrote the database leaves and there is no one who can maintain the software...
[End rant]
-
I've attended the local SQL Server group only once in about four years. The reason is that attention has always been on large scale, enterprise level databases. The statement that small scale setups compose the vast majority of cases out there comes as a shock to me, though logically it makes sense.
I'm part of an organization that has been using MSDE on laptops for years. I don't know of anyone else that does that...maybe I should write about it one of these days.
Steve Miller -
Good, no nonesense, solid article, Tim - thanks for that.
I count myself as one of the small business users- with SQL 2000 sitting within a partitioned primary server- running a MIS that uses SQL for its data deposit, and utilising Crystal Reports.
With the myriad of rave reviews of SQL2005, and the knowledge that some day I going to have to upgrade - it was nice to read a straight forward, informing article without the hype. ( No criticism intended to any other contributors!)
Lets hope we see more from Tim
-
4 GB for Express actually.
-
So the 2GB limit in MSDE (2GB data + 2GB transaction) is now 4GB in Express (4GB data + 4GB transaction??)... Are you sure the 4GB is not 2GB + 2GB still?
-
Yes... that is what Microsoft reports: 4GB data.
Here's an excerpt from the MSDN site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsse/html/sseoverview.asp
The SQL engine supports 1 CPU, 1 GB RAM, and a 4 GB database size. ... The 4 GB database size limit applies only to data files and not to log files. However, there are no limits to the number of databases that can be attached to the server.
-
You are right - in your link, under the heading
Table 2. Comparison of MSDE with SQL Server Express
it clearly says 4GB for express vs 2GB for MSDE. Good to know - thanks for pointing that out.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply