Electronic Health Records – What’s the Big Deal? (Part 2)
In the first installment of this discussion, I talked about the challenges facing database professionals and others with respect to...
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.
I’m flying out Sunday via Alaska Air, taking the direct flight from Orlando to Seattle, arriving at 11:40 am. If...
If you've ever loaded a 2 GB CSV into pandas just to run a...
By James Serra
What problem is Fabric Ontology trying to solve? For years, most data conversations have...
By Steve Jones
Recently I ran across some code that used a lot of QUOTENAME() calls. A...
Comments posted to this topic are about the item The New Software Team
Comments posted to this topic are about the item Database Mail in SQL Server...
Comments posted to this topic are about the item The string_agg function
We create the following table and then insert some records in it:
create table t1 ( id int primary key, category char(1) not null, product varchar(50) ); insert into t1 values (1, 'A', 'Product 1'), (2, 'A', 'Product 2'), (3, 'A', 'Product 3'), (4, 'B', 'Product 4'), (5, 'B', 'Product 5');What happens if we execute the following query in both Sql Server and PostgreSQL?
select id,
category,
string_agg(product, ';')
over (partition by category order by id
rows between unbounded preceding and unbounded following) as stragg
from t1; See possible answers