March 7, 2013 at 4:31 pm
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉
The only possible reason is so you can say your indexes are SeXI.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
March 7, 2013 at 8:42 pm
Paul White (3/7/2013)
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉The only possible reason is so you can say your indexes are SeXI.
That and to give manufacturers the incentive to make even larger and faster storage devices, CPUs, switches, routers, interfaces, and backup devices.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2013 at 9:13 pm
dwain.c (3/6/2013)
Lynn Pettis (3/6/2013)
Several years ago my oldest daughter's JV soccer coach once confieded "I knew we were in trouble when half the team asked what was offsides?"Well, I've just seen the equivalent here with the question "What is SSMS?"
And you are doing what with SQL Server???
A little knowledge can be a dangerous thing. Be afraid, be very afraid! 😛
LOL
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 7, 2013 at 9:15 pm
Sean Lange (3/7/2013)
Lynn Pettis (3/7/2013)
Sean Lange (3/7/2013)
Lynn Pettis (3/6/2013)
Several years ago my oldest daughter's JV soccer coach once confieded "I knew we were in trouble when half the team asked what was offsides?"Well, I've just seen the equivalent here with the question "What is SSMS?"
And you are doing what with SQL Server???
And I thought only the parents were that clueless about soccer here in the States.
Someday when we are in the same town and have some time, I'll explain the dynamics of soccer in the area I live and why I wasn't surprised by this comment.
I do plan on meeting many of the Threadizens at some point.
I too would like to meet many Threadizens.
Sadly where I live, many of the coaches don't understand offsides. 🙂 I frequently even am forced to remind the "refs" of the rules. For example, last season my team stole the ball after a goal kick and scored. Even though it was our goal I had to remind the ref that a goal kick must get out of the box before the opposing team may touch the ball. One of the refs even once gave a corner to the team by their own goal!!! When I told them they got it wrong they were so confused they tried to give our team a corner.
Oh no, that takes the cake.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 7, 2013 at 9:20 pm
jcrawf02 (3/7/2013)
You're absolutely right, the players should pay attention to what the ref is calling, not what the rules say, because then they know what they can get away with...
Basic rule of most sports involving a referee.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 7, 2013 at 9:25 pm
Jeff Moden (3/7/2013)
Paul White (3/7/2013)
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉The only possible reason is so you can say your indexes are SeXI.
That and to give manufacturers the incentive to make even larger and faster storage devices, CPUs, switches, routers, interfaces, and backup devices.
Don't forget the need for fiber between every endpoint.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 7, 2013 at 9:28 pm
SQLRNNR (3/7/2013)
Jeff Moden (3/7/2013)
Paul White (3/7/2013)
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉The only possible reason is so you can say your indexes are SeXI.
That and to give manufacturers the incentive to make even larger and faster storage devices, CPUs, switches, routers, interfaces, and backup devices.
Don't forget the need for fiber between every endpoint.
I try to make sure there's enough fiber in my diet to avoid any clogs between my endpoints.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
March 7, 2013 at 9:31 pm
SQLRNNR (3/7/2013)
Jeff Moden (3/7/2013)
Paul White (3/7/2013)
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉The only possible reason is so you can say your indexes are SeXI.
That and to give manufacturers the incentive to make even larger and faster storage devices, CPUs, switches, routers, interfaces, and backup devices.
Don't forget the need for fiber between every endpoint.
And remember that XML is the native format for SOAP, and at the time it was introduced it was just GREAT!
Of course, now I am defining the interfaces as JSON.
March 7, 2013 at 9:55 pm
Revenant (3/7/2013)
SQLRNNR (3/7/2013)
Jeff Moden (3/7/2013)
Paul White (3/7/2013)
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉The only possible reason is so you can say your indexes are SeXI.
That and to give manufacturers the incentive to make even larger and faster storage devices, CPUs, switches, routers, interfaces, and backup devices.
Don't forget the need for fiber between every endpoint.
And remember that XML is the native format for SOAP, and at the time it was introduced it was just GREAT!
Of course, now I am defining the interfaces as JSON.
YUCK:sick:
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 8, 2013 at 4:06 am
SQLRNNR (3/7/2013)
Jeff Moden (3/7/2013)
Paul White (3/7/2013)
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉The only possible reason is so you can say your indexes are SeXI.
That and to give manufacturers the incentive to make even larger and faster storage devices, CPUs, switches, routers, interfaces, and backup devices.
Don't forget the need for fiber between every endpoint.
No, fibre's not fast enough to cope with verbose nonsense like XML - just ensure that the signal path between each pair of nodes (not just endpoints, switches and routers too) in the network is good empty vacuum - light's faster in vacuum than in fibre.
Tom
March 8, 2013 at 10:41 am
Jeff Moden (3/7/2013)
Revenant (3/4/2013)
Evil Kraig F (3/4/2013)
Revenant (3/4/2013)
I always find it frustrating when someone asks me or someone else to do things for which T-SQL was not meant, in this case parsing multilevel XML with multiple occurrences of the same tag, yet prohibits use of a tool that would make it a breeze - in this case XML LINQ via CLR Integration.Sorry Revenant. Don't mean to be the cause of your frustration in this case. Clean CLR isn't what scares my DBA's, it's letting my app coders loose with it.
It was not meant at you, Craig. I have been in that situation and I know how it feels.
I feel the same way... I just can't understand why anyone would actually use XML. 😉
Well I'd say XML would be like a lot of other items -it's a tool in the arsenal. Use it correctly and it can be VERY useful; use it badly or in the wrong context, and it blows up in your face.
Kind of like any other tool.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
March 8, 2013 at 8:28 pm
SQLRNNR (3/7/2013)
Jeff Moden (3/7/2013)
Paul White (3/7/2013)
Jeff Moden (3/7/2013)
I just can't understand why anyone would actually use XML. 😉The only possible reason is so you can say your indexes are SeXI.
That and to give manufacturers the incentive to make even larger and faster storage devices, CPUs, switches, routers, interfaces, and backup devices.
Don't forget the need for fiber between every endpoint.
I'm getting old. That now has a double meaning for me. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2013 at 8:45 pm
Matt Miller (#4) (3/8/2013)
Jeff Moden (3/7/2013)
Revenant (3/4/2013)
Evil Kraig F (3/4/2013)
Revenant (3/4/2013)
I always find it frustrating when someone asks me or someone else to do things for which T-SQL was not meant, in this case parsing multilevel XML with multiple occurrences of the same tag, yet prohibits use of a tool that would make it a breeze - in this case XML LINQ via CLR Integration.Sorry Revenant. Don't mean to be the cause of your frustration in this case. Clean CLR isn't what scares my DBA's, it's letting my app coders loose with it.
It was not meant at you, Craig. I have been in that situation and I know how it feels.
I feel the same way... I just can't understand why anyone would actually use XML. 😉
Well I'd say XML would be like a lot of other items -it's a tool in the arsenal. Use it correctly and it can be VERY useful; use it badly or in the wrong context, and it blows up in your face.
Kind of like any other tool.
I strongly agree with the "right tool" sentiment. I just don't agree that XML is the right tool for the transmittal of data destined for a relational database. It seems like using a 100 ton crane to turn a monkey wrench especially when it's used to transmit otherwise flat data for a single database entity. Since I'm mostly a data troll, I've not read up on JSON but if it's a markup language that requires description tags for each row or each element, I'm not going to be very happy with that for data transmission, either.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2013 at 7:11 am
Jeff Moden (3/8/2013)
Matt Miller (#4) (3/8/2013)
Jeff Moden (3/7/2013)
Revenant (3/4/2013)
Evil Kraig F (3/4/2013)
Revenant (3/4/2013)
I always find it frustrating when someone asks me or someone else to do things for which T-SQL was not meant, in this case parsing multilevel XML with multiple occurrences of the same tag, yet prohibits use of a tool that would make it a breeze - in this case XML LINQ via CLR Integration.Sorry Revenant. Don't mean to be the cause of your frustration in this case. Clean CLR isn't what scares my DBA's, it's letting my app coders loose with it.
It was not meant at you, Craig. I have been in that situation and I know how it feels.
I feel the same way... I just can't understand why anyone would actually use XML. 😉
Well I'd say XML would be like a lot of other items -it's a tool in the arsenal. Use it correctly and it can be VERY useful; use it badly or in the wrong context, and it blows up in your face.
Kind of like any other tool.
I strongly agree with the "right tool" sentiment. I just don't agree that XML is the right tool for the transmittal of data destined for a relational database. It seems like using a 100 ton crane to turn a monkey wrench especially when it's used to transmit otherwise flat data for a single database entity. Since I'm mostly a data troll, I've not read up on JSON but if it's a markup language that requires description tags for each row or each element, I'm not going to be very happy with that for data transmission, either.
Well in our case it's more like we're moving the 100-ton crane, dissassembling it in transit and making a whole bunch of 1-ton tractors along the way:). The XML is very useful in that, because it allows us some sane way to maintain the relations while the data is in transit, and still have some control over data types etc.... Besides - we leverage an industry-specific interchange spec which was specified using XML, so it also opens us up to all sorts of pre-made tools to help us.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 15 posts - 39,076 through 39,090 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply