T-SQL

External Article

Statistics in SQL: The Kruskal–Wallis Test

  • Article

Before you report your conclusions about your data, have you checked whether your 'actionable' figures occurred by chance? The Kruskal-Wallis test is a safe way of determining whether samples come from the same population, because it is simple and doesn't rely on a normal distribution in the population. This allows you a measure of confidence that your results are 'significant'. Phil Factor explains how to do it.

2017-07-27

6,123 reads

External Article

The Basics of Good T-SQL Coding Style – Part 2: Defining Database Objects

  • Article

Technical debt is a real problem in database development, where corners have been cut in the rush to keep to dates. The result may work but the problems are in the details: such things as inconsistent naming of objects, or of defining columns; sloppy use of data types, archaic syntax or obsolete system functions. With databases, technical debt is even harder to pay back. Robert Sheldon explains how and why you can get it right first time instead.

2017-07-25

5,860 reads

External Article

SQL Server User-Defined Functions

  • Article

User-Defined Functions (UDFs) are an essential part of the database developers' armoury. They are extraordinarily versatile, but just because you can even use scalar UDFs in WHERE clauses, computed columns and check constraints doesn't mean that you should. Multi-statement UDFs come at a cost and it is good to understand all the restrictions and potential drawbacks. Phil Factor gives an overview of User-defined functions: their virtues, vices and their syntax.

2017-07-21

5,686 reads

External Article

Simple SQL: Attribute Splitting

  • Article

If the design of a relational database is wrong, no amount of clever DML SQL will make it work well. Dr. Codd’s Information Principle is that you have, inside the entity tables, the columns that model the attributes of that entity. The columns contain scalar values. Tables that model relationships can have attributes, but they must have references to entities in the schema. You split those attributes at your peril. Joe Celko explains the basics.

2017-07-18

3,822 reads

Blogs

Dazzling Stuff in Databricks (SQL) – Qualify

By

Once upon a time I had a series about some cool stuff in Snowflake:...

Advice I Like: Overnight Success

By

“Most overnight successes – in fact any significant successes – take at least 5...

A CLR Assembly Broke My Availability Group

By

Sounds scary! Did I get your attention?

Read the latest Blogs

Forums

Layanan Resmi BCA KCU BLITAR Telp:0817°825°533

By layanan_Bca88

Telp/Wa 62817825533 Jl. Cempaka No.17, Sukorejo, Kec. Sukorejo, Kota Blitar, Jawa Timur 66111

Kantor Resmi BCA KCU JEMBER Telp:0821°7555°651

By m4rt1n4

Telp/Wa 628217555651 Jl. Gajah Mada No.14-18, Kelurahan Jember Kidu, Jember Kidul, Kec. Kaliwates, Kabupaten...

Why Successful SQL Server Backups Are Not Enough

By Almighty

Comments posted to this topic are about the item Why Successful SQL Server Backups...

Visit the forum

Question of the Day

Adding Bits II

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]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, true)
GO

See possible answers