Allow Port 1433 Ubuntu Linux for SQL Server
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
Getting Started with SQL Server on Linux
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
SQL Summit 2016 Session Feedback.
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.
SQL Server 2016 Compatibility Level
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
Temporary Stored Procedures #sproc
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:
DBCC CheckDB and CheckTable doesn’t check In-Memory OLTP.
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:
- DBCC CHECKDB skips the memory-optimized tables in the database.
- DBCC CHECKTABLE will fail for memory-optimized tables.
Read More »DBCC CheckDB and CheckTable doesn’t check In-Memory OLTP.
Bellingham SQL Server Users Group November Meeting
Bellingham SQL Server Users Group (Pass Chapter) – November 30th at 6:00pm. Features Presentation by Randolph West: “Back up and Restore your Database with Azure… Read More »Bellingham SQL Server Users Group November Meeting
Visualizing VLF’s – Updated
A while back a wrote a blog post with a query to Visualize the VLF’s in your database. Today I have an update to that script.
Here is an updated script that has adds another column called “TextStatus” to the output to give you a better idea of what the different statuses mean. You now get 3 statuses shown, “In Use”, “Available”, and “Available Never Used”. The If you have lots of VLFs that are “Available Never Used” that may be an indication that your log file may be larger than you need. If you don’t have any that are “Available Never Used” the log may be smaller than you need.
When Database Corruption Strikes – Summit 2016
Today I had the pleasure presenting my session “When Database Corruption Strikes” as PASS Summit 2016. I want to thank PASS and the program committee for this great opportunity to present on a topic that I enjoy so much… Database Corruption and how to fix it.
Here is a shot from my point of view about 10 minutes before the session began.
When Database Corruption Strikes – PASS Summit 2016
It has been a great week at PASS Summit 2016. Tomorrow I will be presenting on Database Corruption. The session is called “When Database Corruption Strikes.” … Read More »When Database Corruption Strikes – PASS Summit 2016