External Article

How to Get SQL Server Security Horribly Wrong

It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.

Blogs

5 Starter Projects for Your AI and Data Engineering Portfolio

By

Reading tutorials is fine. Shipping something is better. If you are trying to break...

The Book of Redgate: Taking Breaks

By

We work hard at Redgate, though with a good work-life balance. One interesting observation...

Database AI Agents: The Read-Only Rule

By

Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...

Read the latest Blogs

Forums

BCA KCU RUNGKUT HUBUNGI CS (0817-839-777)

By R4nt4u

WhatsApp: 0817839777, Jl. Raya Kendangsari Industri No.2, Kendangsari, Kec. Tenggilis Mejoyo, Surabaya, Jawa Timur...

BCA KCU KEDIRI HUBUNGI CS (0817-839-777)

By layanan_Bca88

WhatsApp: 0817839777, Jl. Brawijaya No.8, Pocanan, Kec. Kota, Kota Kediri, Jawa Timur 64123

BCA KCU GALAXY HUBUNGI CS (0817-839-777)

By m4rt1n4

WhatsApp: 0817839777, Jl. Dr. Ir. H. Soekarno No.37-39, Klampis Ngasem, Kec. Sukolilo, Surabaya, Jawa...

Visit the forum

Question of the Day

Running SQLCMD II

I run this command to start SQLCMD:

sqlcmd -S localhost -E -c "proceed"
At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version
2> go
What happens?

See possible answers