2003-08-06
2,373 reads
2003-08-06
2,373 reads
2003-08-04
3,109 reads
Andy returns to the Worst Practice series this week with a short article looking at how connection strings in applications affect what you see in sysprocesses. Perhaps less controversial (in our opinion) that some of the other worst practices, this is something easy to fix and definitely worth fixing! Read the article and post a comment - explore other points of view! Readers posting a comment will be entered in a drawing for a copy of the SQL Server 2000 Resource Kit.
2003-08-01
15,790 reads
2003-07-31
2,434 reads
2003-07-30
1,969 reads
2003-07-28
2,540 reads
2003-07-25
2,632 reads
2003-07-21
2,957 reads
2003-07-17
3,340 reads
2003-07-16
2,679 reads
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...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WA:08218154393 Jl. Matraman Raya No.14-16, RT.2/RW.1, Kb. Manggis, Kec. Matraman, Kota Jakarta Timur, Daerah...
WA:08218154393 Jl. HOS Cokro Aminoto No.56-58, Muka, Kec. Cianjur, Kabupaten Cianjur, Jawa Barat 43215
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