2010-03-11
4,763 reads
2010-03-11
4,763 reads
2010-03-09
4,383 reads
A lot of the time, the key to making SQL databases perform well is to take a break from the keyboard and rethink the way of approaching the problem; and rethinking in terms of a set-based declarative approach. Joe takes a simple discussion abut a problem with a UDF to illustrate the point that ingrained procedural reflexes can often prevent us from seeing simpler set-based techniques.
2010-03-09
3,459 reads
2010-03-08
4,688 reads
2010-03-02
4,085 reads
Seth Delconte brings us a technique to solve a common request. Using the NEWID function to return a random record from a result set.
2010-03-01
7,495 reads
2010-02-22
3,847 reads
Rob Gravelle takes a complex SQL statement and shows you several ways to re-write it that both simplifies and shortens it, while still yielding the same results.
2010-02-22
4,532 reads
Cleaning up garbage from data can be a big problem for a developer.Check out a simple solution from Shubhajyoti Ghosh to cleaning up garbage from data.
2010-02-22
10,872 reads
2010-02-12
4,403 reads
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