SQL Server 2005 has changed many of the ways in which we will use SQL Server in the future with a dizzying array of new features and enhancements. Sureshkumar Ramakrishnan brings us the second part in a series looking at what these changes do and how to use them.
2007-11-28 (first published: 2006-12-06)
20,440 reads
SQL Server 2005 has changed many of the ways in which we will use SQL Server in the future with a dizzying array of new features and enhancements. Sureshkumar Ramakrishnan brings us the first part in a series looking at what these changes do and how to use them.
2007-11-27 (first published: 2006-11-29)
27,955 reads
Data cleansing is something that constantly occurs in all RDBMSes, not just SQL Server. However it's easier on some platforms than others. New Author Sureshkumar Ramakrishnan has written a script that shows how you can easily remove duplicate rows in SQL Server. Read about his technique and see if it might come in handy in your environment..
2007-10-02 (first published: 2004-12-20)
47,424 reads
SQL Server 2000 has a great scheduler in SQL Agent, but it isn't integrated with anything else. And with lots of servers, having a centralized environment is essential to keeping yourself from being overworked. Author Sureshkumar Ramakrishnan brings us his technique for running SQL Server jobs from an external scheduler.
2005-08-24
14,511 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...
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