Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Would You Choose SQL Server? Expand / Collapse
Author
Message
Posted Thursday, August 8, 2013 8:30 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 11:10 AM
Points: 31,279, Visits: 15,738
Comments posted to this topic are about the item Would You Choose SQL Server?






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1482624
Posted Thursday, August 8, 2013 9:51 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 11:04 AM
Points: 35,546, Visits: 32,140
I have to say "it depends" on what the app is supposed to do (including "scale") and how specialized it needs to be. Having written a small and specialized "data engine", including my own sort routines, clustered and nonclustered indexes (non B-Tree), date/time functions, etc, etc, I might not even use a database engine. Of course, I'd also have to weigh out whether doing such a thing were cheaper than buying SQL Server and what the hidden cost of people hating proprietary databases might be. They might not buy the product unless it uses a recognized/established dtabase engine.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1482632
Posted Friday, August 9, 2013 1:50 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 11:48 AM
Points: 2,914, Visits: 1,845
As Jeff says, it depends on the scale.

But if you are talking about a small business startup I'd say use AWS and one of the RDS options as a starting point.

The other thing is to look at your requirements. If you suddenly find that you need an RDBMS and capabilities that look like SSRS, SSAS and SSIS then I'd look at SQL Server. If you only need a small part of the SQL Server eco system then perhaps not.

I'd reitterate that the decision has nothing to do with the quality or lack of features within SQL Server. It is purely on getting an acceptable solution at an acceptable cost to start and grow the business. Remember that a high proportion of business startups fail in the first 18 months.


LinkedIn Profile
Newbie on www.simple-talk.com
Post #1482676
Posted Friday, August 9, 2013 6:13 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 5:48 AM
Points: 318, Visits: 107
So, I'll sort of echo what's already been said...

If we're looking at just the data engine, I'd look at other products, too.

But as soon as the requirements start needing ETL and reporting tools, SQL Server gets a lot more attractive.


Thanks,
MKE Data Guy
Post #1482734
Posted Friday, August 9, 2013 6:15 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 1:14 PM
Points: 2,627, Visits: 4,026
Any decision as to which database to use depends on what the application will do today and for the forseeable future. Even if you are a SQL Server shop, it pays to analyze whether SQL Server is the correct platform. Sometimes the decision is made for you. If the vendor of a package that has already been purchased says the platform is MySQL on Linux then that's what it is.
Post #1482735
Posted Friday, August 9, 2013 11:28 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Thursday, November 20, 2014 3:10 PM
Points: 413, Visits: 1,072
Second David Poole's comments. I am looking at building small apps for researchers and AWS is probably how I'm going to go. Even using free SQL Express wasn't interesting to me.

But for a large enterprise MS SQL would get considered.
Post #1482869
Posted Friday, August 9, 2013 4:55 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:42 AM
Points: 7,851, Visits: 9,602
I guess I have to agree with everything that people have said so far.

However, it's probably worth saying that while MSDE was not really a consideration for anything but trivial applications, SQL Express is much more useful. So there's a class of app for which SQL express is adequate, and it's certainly difficult to claim that the license for that is too expensive.

I think some of the changes in licensing recently have made SQL Server much less competitive that it used to be. If I understand the increased costs correctly, there are many cases where a couple of years ago I would have recommended SQL Server but today I would recommend Postgres.


Tom
Post #1482975
Posted Friday, August 9, 2013 9:32 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 1:14 PM
Points: 11, Visits: 274
No I would not buy SQL Standard to build the app on the hardware you describe. I would by Developer Edition write the SQL code in ANSI standard and then load test it to see what hardware was required and see if I would have enough customers to make it profitable to run on Standard or needed to be ported to another SQL product.
However I completely agree that 2012's licensing was a major step in the wrong direction.
Post #1483003
Posted Friday, August 9, 2013 9:37 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, August 11, 2013 1:28 PM
Points: 2, Visits: 23
Don't even start with the Express version. We started with SQL Standard, then had memory / CPU constraints and moved to SQL Enterprise, being the easier upgrade path. Now pricing is ridiculous and web scale is limited, so we're looking to get out from under the cost/limitations of it. Unfortunately; we have a lot of development, years of it, around MSSQL at this point and migration is difficult. If I had to do it over, I'd find another solution, there are plenty, one that web scaled and was either open source or cost effective at web scale. MSSQL is not!
Post #1483005
Posted Saturday, August 10, 2013 5:03 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 11:11 AM
Points: 10, Visits: 26
Like everything ... it depends. Generally if you are being paid for and paying for (ie have customers and are paying employees salaries) you have to manage some combination of what you are best able to use as a tool and what your customers demand. 8k is not a lot it is about 1 developer month worth of expense. So if you are building anything that you expect to use more than say 6 people months developing the SQL cost is relatively trivial.

If you are a small shop/just starting out try some combination of SQL Express, Azure, or getting hooked up with BizSpark. By the time you need to scale up you should have the revenue to do so. It is all what you as a developer and your customers can support in house. In my experience the expectation is that MySQL/PostGres will be a free/cheap offering and anything on Sybase/DB2/MS SQL etc (the enterprise dbs) will be at "professional" prices. Part of that is they have the built in expense of the database license but I think a part of that is customers mindset IMO too. Give me a computer department ticketing system running on MySQL and I'll assume it is FOSS or try to find a free one. Give my one running on SQL and I'll expect to spend $2000 a year and have someone to call that one time in 10 years I need customer support. If the problem it solves is worth the cost I don't care one way or another make the problem go away and I'll be happy. I suspect most customers are that way too (and the ones not willing to pay a profitable amount for the development cost of the software aren't really customers worth having are they?).
Post #1483064
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse