Five Rules For Successful Conversations With Developers
In this piece, Josh follows up on his earlier article about smoothing DBA/Developer interactions, this time from the side of the developers.
2014-02-07
8,718 reads
In this piece, Josh follows up on his earlier article about smoothing DBA/Developer interactions, this time from the side of the developers.
2014-02-07
8,718 reads
As a developer working with SQL Server, you'll need to work with DBAs at one point or another. Here are some easy ways to make those conversations go smoothly.
2015-04-10 (first published: 2013-09-24)
18,374 reads
To get the IP addresses of Multiple hostnames from below stored procedure.
2015-10-12 (first published: 2013-04-17)
5,813 reads
So you want to be a DBA, but don't know where to start learning what you need to know? R. Barry Young brings you a sixty second guide for how to get moving.
2009-12-04
16,534 reads
SQL Server Essentials Part 1: A look at the key responsibility of a DBA and why it is so vital.
2011-06-10 (first published: 2009-09-14)
24,207 reads
Rodney Landrum describes in his own unique style how he, as a working DBA, goes about troubleshooting problem queries, and investigating various types of locking and blocking problems. In the process, he passes on valuable tips learned from practical, and sometimes stressful, experience.
2009-09-02
6,526 reads
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers