Failover
Too many failovers can cause problems, as can those that happen to often. Steve Jones says you need to consider whether you always need to failover in a sitaution.
Too many failovers can cause problems, as can those that happen to often. Steve Jones says you need to consider whether you always need to failover in a sitaution.
This article compares SELECT INTO and INSERT INTO under different scenarios, and the best approach preferred.
So often, the unexpected delays in delivering database code are more likely to happen after the developers initiate the release process. The necessary checks and tests can turn up surprises: The handover process can expose deficiencies. With good teamwork, planning and forethought, though, the process can be made almost painless.
As database developers, we may need to rethink the way we store and handle personal names
In this latest T-SQL Tuesday, Rob Farley takes a look at a couple of unexpected aspects of query plans you might observe when using Temporal Tables in SQL Server 2016.
Daniel Calbimonte walks through the steps to creating a SQL Server Reporting Services (SSRS) Report from an Analysis Services Tabular Database.
A how-to guide for configuring replication agents after a password change
It's possible to change a software development team and dramatically improve things. Steve Jones highlights an example from Redgate Software.
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