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.
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.
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.
The conclusion of our coverage of the Reporting Services component available in SQL Server 2005 Express Edition discusses systematizing the troubleshooting approach by focusing specifically on performance problems (as opposed to those impacting functionality).
That said, even though my personal focus is pretty much OO, I still miss stuff. SQL Server 2005 came out with the CROSS APPLY and OUTER APPLY operators and I have just started learning how to use APPLY in the last month or so. When I think I have it figured out, I am fortunate enough that some of you are interested in reading about my understanding of the technology.
Take this survey and help out the Managed Provider team at Microsoft.
Here is the script that I used in my Dr. DMV presentation this afternoon at PASS. It is a set...
We are storing large text and URLs that are over 900 bytes in some of our tables and have a requirement to enforce uniqueness in those columns. But SQL Server has a limitation that index size can't be over 900 bytes. How do I enforce uniqueness in these columns and is it possible to achieve this in SQL Server 2005 and above? What are my different options to solve this problem? I heard that we can use CHECKSUM to create a hash, but is it possible to avoid collisions in the hash value as we are storing millions of rows?
Loading EBCDIC data into SQL Server is not a well documented process - this article provides a very useful guide to optimizing the performance of this operation.
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