Posted by jpluimers on 2014/03/19
Interesting: SQL Server 2014 is done: Hekaton, Azure integration « Tim Anderson’s ITWriting.
Most important feature is the in-memory database engine (OLTP).
Because the in-memory OLTP it is so highly optimized there are quite a few T-SQL features missing, but usually it is a magnitude faster than the disk based database engine.
For limitations, see Transact-SQL Constructs Not Supported by In-Memory OLTP.
–jeroen
Posted in Database Development, Development, SQL Server, SQL Server 2014 | Leave a Comment »
Posted by jpluimers on 2014/03/19
Funny way to learn something new:
I hardly use CAST and CONVERT (Transact-SQL), and when I do, it is the standard SQL-92 way.
But a while ago, I came across some code like this:
CONVERT(DATETIME, "31/12/2013", 105);
and wondered what the 105 was.
And it appeared to convert from the Italian date format to DateTime. And that it has been there since at least SQL Server 2000, probably earlier.
Not sure why the passed slashes (/) in stead of dashes (-) as separators though.
There are styles for these groups of conversions:
- Binary
- Date/Time
- Float/Real
- Money/Smallmoney
- XML
Never to old to learn something new (:
–jeroen
Posted in Database Development, Development, SQL Server, SQL Server 2000, SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 | Leave a Comment »
Posted by jpluimers on 2014/03/18
Reminder to self: some great ideas to hunt for memory leaks while your application is running: differencing allocation dumps, DDDebug Memory Profiler, etc.
TURBU Tech » Blog Archive » Wanted: live leak detection for FastMM.
Thanks to the TURBU Tech blog from Mason Wheeler.
–jeroen
Posted in Delphi, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2014/03/13
Listen to Podcast 106: Shipping | iDeveloper.
A few notes:
- RemObjects C# on iOS is based on LLVM, so I assume the other platforms use that too.
- Both guys are really busy shipping stuff, and it is hard.
–jeroen
Posted in .NET, C#, C# 1.0, C# 2.0, C# 3.0, C# 4.0, C# 5.0, Development, RemObjects C#, Software Development | 2 Comments »
Posted by jpluimers on 2014/03/13
Yet another example of somehow who got bitten hard by using the with statement (I decided to give with its own category on my blog).
This time it got shared by Paul Foster on G+ and comes down to this:
Even in unsuspiciously looking code, the wit statement can bite you, especially if you need to do refactoring and (because of that) introduce two names in the same scope.
Or in Paul‘s words:
Whilst upgrading the code to remove the Containers unit (its not supported on NextGen platforms, so I have to make things work with Generics.Collections instead, (bye bye D7 support for this code) and refactor a couple stupidities in my original design (they always creep in, don’t they) I ended up with two class members of the same name. The with block then looked OK but I was in fact not access the member I thought I was.
–jeroen
via: Paul Foster – Google+ – WITH IS EVIL! God damn it, I know it makes code easier to….
Posted in Borland Pascal, Delphi, Delphi 1, Delphi 2, Delphi 2005, Delphi 2006, Delphi 2007, Delphi 2009, Delphi 2010, Delphi 3, Delphi 4, Delphi 5, Delphi 6, Delphi 7, Delphi 8, Delphi x64, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Development, Pascal, Software Development, Turbo Pascal, With statement | 18 Comments »