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 Wednesday, November 20, 2013 8:45 PM


SSC-Dedicated

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

Group: Administrators
Last Login: Today @ 12:11 PM
Points: 31,018, Visits: 15,455
Comments posted to this topic are about the item What is SQL Server not good at?






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1516302
Posted Wednesday, November 20, 2013 10:11 PM


SSC-Dedicated

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

Group: General Forum Members
Last Login: Today @ 1:47 PM
Points: 35,215, Visits: 31,667
The article link in the post above doesn't work. It takes me to a "Not found" window.

--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 #1516315
Posted Thursday, November 21, 2013 12:49 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 8:29 AM
Points: 12,945, Visits: 10,716
You can find the article in the daily newsletter. Can't find it on the site though.

What's SQL Server not good at?
SSRS and SSIS could certainly improve a lot in regards to usability. Especially SSRS lacks some very basic features, such as a decent configuration of prompts and even "justify text" is missing.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1516339
Posted Thursday, November 21, 2013 2:23 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:37 AM
Points: 5,425, Visits: 3,161
I guess it could be a question of emphasis. Surely it would be to the advantage of Microsoft to give a greater impression of openness, clarity and helpfulness if they did highlight (particularly common) abuses and poor uses of various features especially if they offered explanations and alternative solutions.

Let's face it, when it isn't done the perpetrator of such implementations will often blame the tool (in this case SQL Server) instead of a misguided use of it i.e. "it can't be my [code/configuration/etc.] that's wrong it must be [SQL Server/SSIS/SSRS/.NET/etc.] that's rubbish".


Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1516354
Posted Thursday, November 21, 2013 6:10 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 8, 2014 5:27 AM
Points: 4, Visits: 49
I think the trouble is that with software, if you can properly state the problem you can usually state the solution in code. It means once you've properly identified a weakness you'll already be halfway to planning the solution. Would you prefer to own up to something people might not even have pinned on you? Or would you just rush to fix it and enjoy the praise for innovation when it's done?

e.g. One of the supposedly inevitable aspects of databases used to be that a lot of locking must occur. What's the solution to too many people and processes reading and altering the same bits of data? Err...don't.. At least find ways to make transactions really quick then keep your fingers crossed. READ UNCOMMITTED is what many still dangerously resort to because of this and even READ COMMITTED doesn't guarantee you consistent data from a given instant in time. Before 2005 do you imagine Microsoft were thinking 'Well, a mostly good solution would be to do like some other DBs and build snapshots in the background and query those". Of course they did but they didn't come out and make a big noise about how the paradigm was fundamentally flawed for high transaction environments. They bided their time till they could get Snapshot Isolation Level implemented. You'd do that yourself if it was your own program and you had pride in it. In a community of eagle-eyed users, you'd be desperate to fix quickly rather than do all the criticism for them.

Adam
Post #1516391
Posted Thursday, November 21, 2013 6:35 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: 2 days ago @ 2:19 PM
Points: 158, Visits: 1,805
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.
Post #1516405
Posted Thursday, November 21, 2013 8:26 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 2:04 PM
Points: 3,572, Visits: 8,008
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.



Luis C.
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

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


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:37 AM
Points: 5,425, Visits: 3,161
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.


That is probably fair comment regarding a significant number, however, a lot of people do at the very least a little research around features that they are about to utilise, especially on new features or those last used a long time ago. I think it is an inadequate reason not to do it on the basis that most people will not pay any attention to it. It would be there for those of use who do read up. Thus marking as out as being different from the rest of the crowd. Otherwise BOL wouldn't exist either.


Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1516463
Posted Thursday, November 21, 2013 9:11 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 11:29 AM
Points: 2,734, Visits: 939
MS hardly admits problems.
As a old joke said "...MS is a marketing corporation with serious software issues"
At forums and MSDN they often use the "its by design" or "its a normative variation" excuses.

IMHO MS SQL Server is by far the most reliable product from MS and today its a mature software full of usefull tools.

But if there are something its not good... maybe its not good for the small shop budget.
I work most with web development where MySQL and Postgre earn great popularity and MS SQL got a reputation of too big, and too expensive.
Maybe we can see more SQL Lite brands (for free) in the future.
Post #1516476
Posted Thursday, November 21, 2013 9:43 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, August 5, 2014 8:27 AM
Points: 217, Visits: 31
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.
Post #1516491
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse