Time to Rebrand
I became a SQL guy back in 1998 because the company that hired me used SQL Server. It’s been a good ride and it’s paid the bills, but after 15 years or so it’s time to do something different.
2015-04-01
6,297 reads
I became a SQL guy back in 1998 because the company that hired me used SQL Server. It’s been a good ride and it’s paid the bills, but after 15 years or so it’s time to do something different.
2015-04-01
6,297 reads
This articles describes two ways to shred Unicode Japanese character from xls files into SQL Server table using SSIS
2015-03-31
1,377 reads
Arshad Ali demonstrates how you can use the command line interface to tune SQL queries and how you can use SQL Server Profiler to capture the workload for tuning with Database Engine Tuning Advisor.
2015-03-31
9,734 reads
This alert is raised when the number of hash warnings events in the last hour goes above a specified threshold. A hash warning event means that part of the data processed for a hash operation was written to tempdb during query execution, which can degrade SQL Server Performance.
2015-03-31
6,894 reads
In which Phil Factor illustrates in TSQL how it is possible to use foreign key constraints to enforce data rules, and illustrates some surprising consequences of using cascading.
2015-03-30
3,124 reads
When you're developing database applications, it pays to check for index scans in the SQL Server query plan cache. Once you've identified the queries, what next? Dennes Torres gives some preliminary guidelines on how to find out why these index scans are being chosen for these queries and how to make the queries run faster and more efficiently.
2015-03-30
9,858 reads
I had an update statement that took 3 minutes to run after this code change it took 6 seconds.
2015-03-27 (first published: 2014-05-08)
35,088 reads
In this article, Robin Shahan talks about security and how to control access to containers and blobs using shared access signatures (SAS) and stored access policies.
2015-03-27
7,596 reads
'Temporal' tables contain facts that are valid for a period of time. When they are used for financial information they have to be very well constrained to prevent errors getting in and causing incorrect reporting. This makes them more difficult to maintain. Is it possible to have both the stringent constraints and simple CRUD operations? Well, yes. Dwain Camps patiently explains the whole process.
2015-03-26
9,819 reads
SQL Saturday, organized by SQL South West, is coming to Exeter, England on April 25. This is sure to be a special event, and as always, offers a free day of training and networking. Register while space is available.
2015-03-26
7,920 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