Writing Custom Rules for FxCop
FxCop is a useful tool for analyzing code to highlight potential issues and deviations from best practise. To fully utilize to power of FxCop, custom rules can be added to the inbuilt rules that ship with FxCop.
FxCop is a useful tool for analyzing code to highlight potential issues and deviations from best practise. To fully utilize to power of FxCop, custom rules can be added to the inbuilt rules that ship with FxCop.
With the PASS Summit taking place last week in Seattle, Steve Jones found that there was a tremendous amount of SQL Server news and information on Twitter. It's a medium that is becoming useful for SQL DBAs.
A litmus test is a way of determining your answer to a question based on a single issue or response. Steve Jones sees this as a bad idea, especially when looking to hire technical people.
Indexing is important for improving performance, but do you know that a lack of indexes might actually cause things to stop working? Alok Dwivedi brings us a very interesting scenario where the lack of an index causes a problem with concurrency.
A litmus test is a way of determining your answer to a question based on a single issue or response. Steve Jones sees this as a bad idea, especially when looking to hire technical people.
A litmus test is a way of determining your answer to a question based on a single issue or response. Steve Jones sees this as a bad idea, especially when looking to hire technical people.
A litmus test is a way of determining your answer to a question based on a single issue or response. Steve Jones sees this as a bad idea, especially when looking to hire technical people.
Recently, I was at a conference, and I heard the following discussion about what a data warehouse was. One person suggested that a data warehouse was really all the old legacy systems connected by software that could access the data. By calling such a contraption a data warehouse, the organization could avoid having to do the hard and complex work of integration. There are so many problems with this federated approach to a data warehouse that they are almost not worth repeating here. But (once again!) here goes.
The transaction log is a fairly complex construct in SQL Server and present in every database installation. New author James Rea brings us a great introduction to how the log works and how to maintain it.
Steve Jones has attended the PASS Summit annually, and found value. But for this Friday's poll, did you find value this week? Or have you in the past? Let others know.
By James Serra
Most enterprise questions do not live neatly in one place. The numbers may be...
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
Telp/Wa 62 8218200233 PQHX+93W, Jl. RS. Fatmawati Raya No.6 A, RT.1/RW.5, Cipete Sel., Kec....
Telp/Wa 62 8218200203 Gedung Gajah Tebet, Jl. Dr. Saharjo No.Raya 111 Unit N &...
Telp/Wa:62 8218200174 Jl. Tebet Barat IX No.40, RT.6/RW.4, Tebet Bar., Kec. Tebet, Kota Jakarta...
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers