Centrally collect replication conflicts and send an alert
Automatically capture replication conflicts and generate an automated email notification.
2016-02-05 (first published: 2011-10-17)
3,928 reads
Automatically capture replication conflicts and generate an automated email notification.
2016-02-05 (first published: 2011-10-17)
3,928 reads
Read this tip to learn how to import data from multiple Excel worksheets into SQL Server using SSIS.
2016-02-05
4,291 reads
An evaluation of the SQL Azure Database Performance Levels recommended by the DTU Calculator service, and a comparison with on premise SQL Server performance.
2016-02-04
3,764 reads
In-Memory OLTP has evolved to be a great solution. However, a production system that uses it needs careful monitoring to avoid stress conditions becoming problems. As with many new features of SQL Server, it pays to plan a monitoring strategy to ensure that you are alerted as soon as possible when things go awry.
2016-02-04
3,523 reads
Jeremy Kadlec introduces the Enhanced Data Integration Suite (EDIS), a SQL Server T-SQL stored procedure based solution to automate, manage, and audit ETL processes so you no longer have to manually build SSIS Packages.
2016-02-03
6,164 reads
From an IT infrastructure and compliance perspective, the importance of protecting data is clear. But it also has profound business implications and can even be a competitive differentiator by helping drive customer loyalty and retention. David Hobbs-Mallyon talks about Microsoft’s approach to data security.
2016-02-02
3,545 reads
Learn a quick method to find and remove duplicate records in your SQL Server tables.
2016-02-01
9,862 reads
When starting out with PowerShell, it is hard to escape from the detail to work out the best strategy for creating scripts. Laerte Junior explains how, when and why it pays to think in terms of versatile functions to meet varying demands.
2016-02-01
3,169 reads
This article talks about using the statistical program, R, for applying simple statistics against data in Microsoft SQL Server.
2016-01-29 (first published: 2014-03-10)
13,849 reads
One of the most important features of the SQL Server 2016's new Query Store is the reporting. With these features, it is now possible to get a wealth of information on how your query workload is performing, either aggregated for the entire query workload or for a single query. With this information, you can see the effects of 'forcing' an execution plan for specific queries and get feedback of the consequences.
2016-01-29
4,359 reads
Recently, in an attempt to thwart leechers (1990s kids will know), I added some...
Once upon a time I had a series about some cool stuff in Snowflake:...
By Steve Jones
“Most overnight successes – in fact any significant successes – take at least 5...
Comments posted to this topic are about the item Why Successful SQL Server Backups...
Comments posted to this topic are about the item Adding Bits II
Comments posted to this topic are about the item An Unlimited Token Budget
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, true)
GO
See possible answers