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 ««123»»

What is SQL Server not good at? Expand / Collapse
Author
Message
Posted Thursday, November 21, 2013 9:50 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 2:03 PM
Points: 1,334, Visits: 3,069
steve_seeley (11/21/2013)
To quote the favorite answer of technical people everywhere, "It depends". I can take a simple select statement and if I miss something in the where clause I can tank the server. Does that mean we should put warning signs all over? SQL Server is a tool. I can use a screwdriver to drill a hole but it won't be done neatly or easily. There are too many ways to misuse any tool and get bad results. While I do think that it is nice to know limitations or shortcomings sometimes I feel that I am better off not knowing.


Tools can be misused and in some cases downright dangerous in the wrong hands.


"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ..."
Post #1516497
Posted Thursday, November 21, 2013 10:18 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, November 3, 2014 4:28 PM
Points: 17, Visits: 121
What SQL Server doesn't do well (or at all) is true active-active clustering for the purpose of load balancing. I think the lack of a solution there is leading people to look at Oracle or (gasp!) Cassandra as better database solutions.
Post #1516500
Posted Thursday, November 21, 2013 10:34 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 8:11 AM
Points: 5,886, Visits: 13,043
SQL server is not good at scale-out (in particular), or DR, 2012 always on is getting there but its still complex.

This is because SQL is so tied to the servername and metadata is held outside the database in system databases.

A simple database engine only instance is OK but as soon as you start adding SSIS, SSRS, linked servers etc it gets messy quickly to maintain failover servers.

MS tend to gloss over this.


---------------------------------------------------------------------

Post #1516508
Posted Thursday, November 21, 2013 10:47 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 2:18 PM
Points: 235, Visits: 2,250
Backup and restore require far too much hands on DBA work. I've mentioned this before here, but back in the 1980's, mainframe DB2 just required a restore database statement to some point in time, and it took care of the rest. The DBMS knew about all of the backup and log files, and did whatever roll back and roll forward that was necessary. Object level recovery should not require a 3rd party vendor product.

Oracle's GoldenGate walks all over replication. It queues up the replicated data, can easily be monitored, and is easily restartable when something goes wrong. It supports many DBMS', and can be used for SQL Server -> SQL Server replication.

The built in monitoring tools are primitive. Quest/Dell even give away a basic version of SQL Spotlight called Spotlight Essentials. Microsoft should include the equivalent of all of the free 'lite' versions.

Post #1516516
Posted Thursday, November 21, 2013 10:54 AM


SSC-Dedicated

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

Group: Administrators
Last Login: Today @ 7:12 AM
Points: 31,284, Visits: 15,746
Jeff Moden (11/20/2013)
The article link in the post above doesn't work. It takes me to a "Not found" window.


Do you mean the URL to the editorial? Or the one to the article I referenced? Both work for me. They're here:

Editorial: http://www.sqlservercentral.com/articles/Editorial/104983/
Article: http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1516518
Posted Thursday, November 21, 2013 10:55 AM


SSC-Dedicated

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

Group: Administrators
Last Login: Today @ 7:12 AM
Points: 31,284, Visits: 15,746
Robert.Sterbal (11/21/2013)
I tend to rely on google and experience, as well as one on one interaction to address the issue that you raised here. It is the nature of the form of documentation that it is a bad place to put what the limitations are. Makes it too easy for competitors to attack your business.


But everyone has limitations, and the fact that some features don't work for some situations isn't a place to attack things. I'm sure competitors would attack, but it would be a shallow, straw man attack. I suspect that most developers would look past such silliness.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1516519
Posted Thursday, November 21, 2013 11:14 AM


SSC-Addicted

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

Group: General Forum Members
Last Login: Today @ 10:56 AM
Points: 440, Visits: 600
What is SQL server not good at? SSIS (sorry, I know that is too general)

At least there should be documentation and warnings about the import issues that have persisted through various versions of the product and that MS is unlikely to fix or patch. I'm sure I'm not the only person who has spent hours or days researching an error message only to find out that the issue is a documented bug (but usually on a non-MS site like this one.)

So really my answer is MS is not good at honesty about known issues. There should be a central repository to list known issues and suggested work-arounds.
Post #1516527
Posted Thursday, November 21, 2013 11:26 AM


SSC-Dedicated

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

Group: Administrators
Last Login: Today @ 7:12 AM
Points: 31,284, Visits: 15,746
Luis Cazares (11/21/2013)
Even if it's included in BOL, would people read the warnings?
Most people having bad coding habits won't even read basic documentation and go for what they suppose is better with no real bases.


Some of us would for sure.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1516533
Posted Thursday, November 21, 2013 12:17 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 2:42 PM
Points: 175, Visits: 1,876
Whatever problems open source software has, per unit/device/client licensing is very costly to scale.
Post #1516549
Posted Thursday, November 21, 2013 2:31 PM


SSC-Dedicated

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

Group: General Forum Members
Last Login: Today @ 12:06 PM
Points: 35,572, Visits: 32,164
Steve Jones - SSC Editor (11/21/2013)
Jeff Moden (11/20/2013)
The article link in the post above doesn't work. It takes me to a "Not found" window.


Do you mean the URL to the editorial? Or the one to the article I referenced? Both work for me. They're here:

Editorial: http://www.sqlservercentral.com/articles/Editorial/104983/
Article: http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/


It was in the original post of this thread. I must have caught it right while you were setting it up because it works fine now.


--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 #1516586
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse