Today I am presenting one of my favorite sessions “When Database Corruption Strikes” remotely for the PASS Calgary SQL Server Users Group. This is the… Read More »When Database Corruption Strikes – Calgary SQL Users Group
With SQL Server now being available (pre-release) on Linux, I think we will see many SQL DBA’s who previously did not have Linux experience being… Read More »Linux commands for SQL DBA’s who don’t know Linux (yet)
If you have just installed SQL Server on Ubuntu Linux and you are trying to connect remotely you may have some difficulty connecting if port… Read More »Allow Port 1433 Ubuntu Linux for SQL Server
With the recent public availability of the SQL Server Linux release, I figured I should give it a try, and it went well. Here is… Read More »Getting Started with SQL Server on Linux
I was extremely excited to get my session feedback from my SQL PASS Summit 2016 session on Database Corruption today. I have been waiting, and… Read More »SQL Summit 2016 Session Feedback.
With SQL Server 2016, there was a new compatibility level introduced, level 130 the new SQL Server 2016 Compatibility Level. SQL Server can run in a… Read More »SQL Server 2016 Compatibility Level
CREATE PROCEDURE #MyProcedureName
Yes, you can create temporary stored procedures by prefixing the name of the sproc with a #. The temporary stored procedure is sort of a “leave no trace” stored procedure that is only good for your session. If you use double ## you will get a global temporary stored procedure.
For instance:
Special thanks to my friend Theresa Iserman for introducing me to Jos de Bruijn the Senior Program Manager for the In Memory OLTP (Hekaton) project to help get my questions answered at PASS Summit.
So, the Hekaton – In Memory OLTP tables are perhaps one of the most amazing performance improvements to SQL OLTP in a long time. The way that they are managing data with no latches, locks or spinlocks is awesome, and the performance gains are great.
However in a recent session at Pass Summit 2016 with Bob Ward, I followed up with a question on CheckDB and In Memory OLTP tables. Since the data for these are not store in the normal SQL Server data files or even in regular pages. Bob confirmed that CheckDB (and CheckTable) does not check the data associated with the In Memory OLTP tables. I even confirmed this from Books Online in a post called “Transact SQL Constructs Not Supported by In-Memory OLTP” which stated the following:
Read More »DBCC CheckDB and CheckTable doesn’t check In-Memory OLTP.