One of the very common things that is needed in SQL Server is performing a restore of a database. It's also one of the most important things that needs to take place. So why isn't this a simpler process? Steve Jones wonders why we can't make this a simpler process.
In the first installment of this discussion, I talked about the challenges facing database professionals and others with respect to...
There are many ways to perform disaster recovery with Microsoft SQL Server Reporting Services (SSRS). Based upon customer experience and internal testing, this technical note provides guidance around best practices to design and manage robust end-to-end disaster recovery (DR). This DR method will involve both automatic and manual failover in the form of content switches, SQL Server failover clustering, and database mirroring. This case study focuses on the lessons learned from CareGroup Healthcare System.
This paper discusses the integration of SAP NetWeaver BI ® with Microsoft ® SQL Server ® 2008 Reporting Services (SSRS). The paper provides an overview of using the Reporting Services SAP Netweaver BI data provider and related query designer, to build high quality reports against SAP NetWeaver BI sources. For Reporting Services users who are new to working with SAP NetWeaver BI, this paper will help you connect and build datasets. For users already familiar with SAP NetWeaver, the paper will show how some of that system’s notable features can be leveraged in Reporting Services reports. It also presents some tips and tricks that can help you make the most of the integration between the two products.
One of the very common things that is needed in SQL Server is performing a restore of a database. It's also one of the most important things that needs to take place. So why isn't this a simpler process? Steve Jones wonders why we can't make this a simpler process.
One of the very common things that is needed in SQL Server is performing a restore of a database. It's also one of the most important things that needs to take place. So why isn't this a simpler process? Steve Jones wonders why we can't make this a simpler process.
One of the very common things that is needed in SQL Server is performing a restore of a database. It's also one of the most important things that needs to take place. So why isn't this a simpler process? Steve Jones wonders why we can't make this a simpler process.
How can you delete only some duplicates? Without Identity's, Temp tables, Cursors, loops or ROW_NUMBER()? Would you believe, go back to the 70's?
This article from Divya Agrawal might help you to overcome the problem when multiple objects or statements are scripted together. This is technique that can eliminate errors from scripts built dynamically.
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