Cómo crear un instalador de SQL Server 2012 con CU1 integrado (Product Updates – Slipstream)

For English version visit this link How to create an SQL Server 2012 installer with integrated CU1 (Product Updates – Slipstream)
 
Hace un tiempo, creé un fichero batch para crear un Instalador SQL Server 2008 R2 con SP1 Integrado, conocido como Slipstream, ahora en SQL Server 2012 esto ha sido reemplazado con una nueva funcionalidad llamada Product Updates.
 
Con la funcionalidad Product Updates podemos integrar los Service Pack o Cumulative Updates al instalador de SQL Server, con esto ahorramos mucho tiempo, sobre todo cuando hay que hacer múltiples instalaciones.
  
Read more of this post

How to create an SQL Server 2012 installer with integrated CU1 (Product Updates – Slipstream)

For Spanish version visit this link Cómo crear un instalador de SQL Server 2012 con CU1 integrado (Product Updates – Slipstream)
 
Time ago, I created an automated batch procedure to create an SQL Server 2008 R2 Installer with Integrated SP1, known as Slipstream, now in SQL Server 2012 this was replaced with a new funcionality called Product Updates.
 
With the Product Updates funcionality we can integrate Service Pack or Cumulative Updates to the SQL Server installer, this save much time, specially when you need to do multiple installations.
 
Read more of this post

Error al actualizar tabla con columna rowguid

For English version visit this link Error updating table with rowguidcol
 
En uno de nuestros entornos, tenemos dos BBDD SQL Server 2008 R2 alineadas entre si por replica Peer to Peer, y a su vez cada BBDD tiene creada una replicación de Mezcla con varios subscriptores.
 
Cuando tratamos de realizar un update en un artículo/tabla que está en la publicación de Mezcla y en la publicación Peer to Peer nos muestra el siguiente error:
  Read more of this post

Error updating table with rowguidcol

For Spanish version visit this link Error al actualizar tabla con columna rowguid
 
In one of our environments, we have two SQL Server 2008 R2 DB aligned together by Peer to Peer replication, and each of the databases have a Merge replication with multiple subscribers.
 
When we try to make an update on a article/table that is published in Merge and Peer to Peer shows this error:
  Read more of this post

Quick way to create a SQL Server 2008 R2 installer with integrated SP1 (Slipstream)

For Spanish version visit this link Forma rápida de crear un instalador de SQL Server 2008 R2 con SP1 integrado (Slipstream)
 
With the Slipstream funcionality we can integrate Service Pack or Cumulative Updates to the SQL Server installer, this save much time, specially when you need to do multiple installations.
 
This guide is a modification of How to slipstream SQL Server 2008 R2 and a SQL Server 2008 R2 Service Pack 1 (SP1), to which I add a .bat file to save time.
 
This guide is for the English version of SQL Server 2008 R2.
  Read more of this post

¿Cómo saber que tablas están replicadas?

For English version visit this link How to know which tables are replicated?
 
A veces es necesario conocer todas las tablas que están replicadas en una BBDD, para ello utiliza estos scripts, ejecutar en la BBDD que este replicada:
--Que tablas están publicadas en Réplica de Mezcla y sus subscriptores
SELECT
b.name AS [Table],
DB_NAME() AS PublisherDB,
a.subscriber_server AS Subscriber,
a.db_name AS SubscriberDB
from sysmergesubscriptions a, sysmergearticles b
where a.pubid=b.pubid
order by a.subscriber_server

--Que tablas están publicadas en Réplica Transaccional y sus subscriptores
SELECT
a.name AS [Table],
is_published AS is_tran_published,
DB_NAME() AS PublisherDB,
c.srvname AS Subscriber,
c.dest_db AS SubscriberDB
FROM sys.tables a
INNER JOIN dbo.sysarticles b ON a.object_id = b.objid
INNER JOIN dbo.syssubscriptions c ON b.artid = c.artid
WHERE is_published = 1

How to know which tables are replicated?

For Spanish version visit this link ¿Cómo saber que tablas están replicadas?
 
Sometimes you need to know all the tables that are replicated in a DB, for that use this scripts, run it in the replicated DB:
--Which tables are published for Merge Replication and his subscribers
SELECT
b.name AS [Table],
DB_NAME() AS PublisherDB,
a.subscriber_server AS Subscriber,
a.db_name AS SubscriberDB
from sysmergesubscriptions a, sysmergearticles b
where a.pubid=b.pubid
order by a.subscriber_server

--Which tables are published for Transactional Replication and his subscribers
SELECT
a.name AS [Table],
is_published AS is_tran_published,
DB_NAME() AS PublisherDB,
c.srvname AS Subscriber,
c.dest_db AS SubscriberDB
FROM sys.tables a
INNER JOIN dbo.sysarticles b ON a.object_id = b.objid
INNER JOIN dbo.syssubscriptions c ON b.artid = c.artid
WHERE is_published = 1