What I learned in the last year? Resources and websites that help you get started with SQL Server

For Spanish version visit this link ¿Qué he aprendido en el último año? Recursos y webs que te ayudarán a comenzar con SQL Server
Within days, June 20th, will be one year since I joined Avanade Spain, so I think that is a good moment to stop and think over all learned in the last 366 days.
I can safely say that this was the year that I’ve grown more as SQL Server professional, When I started at company, didn’t know practicaly how a cluster works; the replication seemed a world apart; I wasn’t familiar with SQL Scripting; and my English level was much worse (you can see how badly I write, but before was even worse).
I got my new knowledges in a big part thanks to my father, my co-workers, Google, MSDN forums, and blogs that saved my life a lot of times, I going to enumerate some of this:
  Read more of this post

The merge process was unable to create a new generation at the ‘Publisher’

For Spanish version visit this link El proceso de mezcla no pudo crear una nueva generación en ‘Publisher’
Yesterday we did an massive update of 1 million of registers in a table of the replication DB, after the update , we started the replication of one computer, and we saw a failure in the first publication after 2000 seconds, showing the next error:
“The merge process was unable to create a new generation at the ‘Publisher’. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write.”
Read more of this post

Rollback process for a failed SQL Server Cluster Instance migration

For Spanish version visit this link Proceso de marcha atrás para una migración fallida de Instancia en Cluster SQL Server
Take a practical case in which have to migrate a production SQL Server instance from Windows Server 2003 Cluster to Windows Server 2008 Cluster.
One of the first steps for a migration is shut down the SQL Cluster service and delete the name of the SQL Cluster in the Active Directory, because if we not doing this, the Windows Server 2008 Cluster that we create will find a duplicate name when try to create the SQL Cluster, here we find a problem if in the middle of the migration had to rollback, because the SQL Server resource in the Windows Server 2003 Cluster not will start.
  Read more of this post

Automatic change “Max Server Memory” value if a Failover occurs

For Spanish version visit this link Cambiar automáticamente el valor de “Max Server Memory” si ocurre un Failover
In one of our environments, we have a cluster with two active-active nodes with one SQL Server instance in each one.
During this week, a fail of the service occurred in one of the nodes, which caused a failover to the node that was available.
The problem that we found was that the node only have 25GB of RAM memory and the value of “Max Server Memory” assigned for each instance was 20GB, so we have the risk that if the two instances beginning to need more RAM memory would come a moment that the Windows OS would lose performance.
  Read more of this post

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
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
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