|
|
Thanks for the link. It is probably reasonably reliable - but I guess that it takes some fancy encoding and error correction to go almost four kilometers through plankton, currents, microplastics, fish schools ...
I am not sure about the interpretation of "The Titan would have had ...", though. A corresponding wording in Norwegian, "Titan skal ha hatt ..." should be read as "We have heard this as a rumor, but don't nail us if it turns out to be incorrect!" Maybe "would have had" is more reliable
|
|
|
|
|
In 2009, we had gone in a sub, to a depth of about 120 feet off the coast of Mauritius. Luckily we came up as planned.
|
|
|
|
|
I am reading the book from Itzik on T-SQL about logical query processing. it is really good.
my question is: Is this logical query processing the same for Teradata SQL?
diligent hands rule....
modified 19-Jun-23 19:40pm.
|
|
|
|
|
I don't know what, "logical query processing", means.
|
|
|
|
|
It's the bit that analyses and defines the order of processing in the from part.
|
|
|
|
|
It's the opposite of "illogical query processing"
|
|
|
|
|
Not to mention that how ever you masterfully create your query, internally, SQL Server optimizes it behind the scenes and creates its own execution plan.
|
|
|
|
|
I've discovered that if you pay attention to the execution plans you can usually improve your query performance by forcing the T-SQL query optimizer to select different pathways.
|
|
|
|
|
it is the internals about how T-SQL is logically executed before SQL optimization.
diligent hands rule....
|
|
|
|
|
PIEBALDconsult wrote: I don't know what, "logical query processing", means. In other words, his question was an illogical query that couldn't be processed?
|
|
|
|
|
Southmountain wrote: Teradata SQL
I didn't even know Teradata SQL[^] was a real thing. I figured you were just guessing at the "T", like it could be Pterodactyl[^] SQL.
|
|
|
|
|
thanks for the first link!
diligent hands rule....
|
|
|
|
|
Southmountain wrote: Is this logical query processing the same for Teradata SQL?
Unlikely.
Even if the vendor was the same it would be unlikely.
The factors is systems like these.
1. Age. How long the product has existed.
2. Specifics of the application
3. Presumptions from the developers about how it will be used
4. Acquired knowledge about how it is used.
All of those lead to solutions that attempt to increase performance. So the implementations are different.
Could it be the same? I seriously doubt that. Even if someone stole the code it would still end up different over time.
Could there be similarities? Yes.
So presumably you are asking if the book you are reading might help you with understanding the other. So the last point makes it possible.
|
|
|
|
|
How many of you are still using Linq-To-SQL versus Entity Framework?
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
Never neither.
I just use straight ADO.net for access to whatever database system I need to connect to.
If I understand correctly, those connect only to SQL Server.
Using ADO.net allows an application to connect to multiple database systems, even allowing the user to specify which at run time if the application is written that way.
|
|
|
|
|
What are you using?
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
PIEBALDconsult wrote: If I understand correctly, those connect only to SQL Server. You understand incorrectly then.
EF uses ADO.NET under the hood and also supports SQLite, MySQL, PostgreSQL, Azure Cosmos DB, Firebird, Oracle...
PIEBALDconsult wrote: Using ADO.net allows an application to connect to multiple database systems, even allowing the user to specify which at run time if the application is written that way. How often is that a requirement?
|
|
|
|
|
More often for me than for others probably.
|
|
|
|
|
Well, still possible using EF.
|
|
|
|
|
|
Imagine you'd learn something new.
|
|
|
|
|
I use all three:
Dapper
Linq2SQL
EF
Depends on the project, but the combination is only Dapper+Linq2SQL or Dapper+EF.
Much of what I do is highly abstracted, SQL generated on the fly, so Dapper is a godsend. And unless I'm doing business logic on something, mirroring the models in C# is just stupid, in my opinionated opinion.
|
|
|
|
|
Marc Clifton wrote: SQL generated on the fly
I don't do that very often, but I may accept SQL from a script or the command line.
|
|
|
|
|
Marc Clifton wrote: Dapper
Linq2SQL
EF
We use these 3 as well in our shop.
|
|
|
|