(Erin Stellato) SQL Server introduced In-Memory OLTP objects in SQL Server 2014. There were many limitations in the initial release; some have been addressed in SQL Server 2016, and it’s expected that more will be addressed in the next release as the feature continues to evolve.
Tag: sql server
SQL Server Workgroup Cluster FCM Errors
(Sean Gallardy) One of the new features of SQL Server 2016 is the ability to use SQL Server with Failover Cluster in a workgroup rather than joined to Active Directory. When working with SQL Server and Failover Clustering in a workgroup, many of the abilities that are normally used with Active Direc
UDP vs TCP
(Kenneth Fisher) If you’ve worked much with named instances you’ve probably had to deal with the question “What port is that instance on?”. You probably are aware that the default instance uses port 1433.
SQL SERVER – Alternate to AGENT_DATETIME Function
(Pinal Dave) Sometimes back I posted about interesting function AGENT_DATETIME functions which will convert integers into datetime values. Someone commented that there might be some permission issues using this function which is only available in msdb database.
SQL Server 2016 Integration Services boosted by Linux support
(Brien Posey) As SQL Server changes, so does Integration Services. See the latest SSIS updates, such as added Linux support and an Upgrade Wizard for SQL Server 2016.
The Future For Database Transaction Units
(Thomas LaRock) It was just over three years ago that Microsoft introduced the concept of Database Transaction Units (DTUs).
Copy data to another SQL Server instance without a Linked Server
(Jeffrey Yao) Copying data from a table in one instance to a table in another instance is a common task. You could do this with T-SQL and a Linked Server, but what if you can’t use a Linked Server. To make it more difficult, say I have three servers: A, B, C and I want to copy data from a […]
SQL SERVER – Master Database in Single User Mode – A Serious Issue
(Pinal Dave) There are some weird situations which I see in SQL Server. This is also a one of the surprising situation. One of my clients reported via below screen shot. Let us see the issue of Master Database in Single User Mode.
Script to quickly find SQL Server DBCC CHECKDB Errors
(Eli Leiba) Running DBCC CHECKDBs is something that all DBAs should do, but checking the output for errors can be tedious unless you build a process to identify when deeper investigation needs to be done.
SQL SERVER – FIX : Error: 3456, Severity: 21 – Could not redo log record (xx:xx:xx), for transaction ID (x:xx), on page (x:xx), database ‘master’
(Pinal Dave) While I work on performance tuning most of the time, I do provide consultancy on issues which can be resolved quickly. These are the engagement where I get a lot of content for my blogs as well. Let us learn about the error related to redo log record.
