External Article

One use case for NOT using schema prefixes

I’ve long been a huge advocate for always referencing objects with a schema prefix in SQL Server.

In spite of what may be a controversial title to many of my regular blog readers, I don’t really want you to stop that practice in most of your T-SQL code, because the schema prefix is important and useful most of the time. At Stack Overflow, though, there is a very specific pattern we use where not specifying the schema is beneficial.

Blogs

T-SQLTuesday 204: Are blogs still relevant?

By

This month’s blogging party is hosted by Jeff Ianucci – his challenge is to...

Are Blogs Still Relevant? I Think They Still Are.

By

As for me, I'll keep writing whenever time permits. I don't expect every post...

Reading Blogs: T-SQL Tuesday #204

By

This is an interesting invitation this month. Jeff Ianucci is a new host, and...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Kantor Bank BCA KCU PEKALONGAN Telp:0821°8200°203

By layanan_Bca88

Telp&Wa 628218200203 Jl. Diponegoro No.27, Dukuh, Kec. Pekalongan Utara, Kota Pekalongan, Jawa Tengah 51116

Kantor Resmi BCA KCU MAGELANG Telp:0821°8200°233

By m4rt1n4

Telp/Wa 628218200233 Jl. Ahmad Yani No.1, Magelang, Kec. Magelang Tengah, Kota Magelang, Jawa Tengah...

Visit the forum

Question of the Day

Too Many Choices

I have a table, dbo.MasterBrands, with this data:

BrandID OfficialName
1       Samsung
2       Apple
3       Microsoft
4       Adidas
5       Coca-Cola
I run this query. What is returned for Coca-Cola?
SELECT CHOOSE(BrandID, 'Conglomerate', 'Tech and Design', 'Desktop', 'Apparel')
FROM dbo.MasterBrands;

See possible answers