SQL transaction log unexpecting grow on my published database

Problem description: The transaction log grow up without end.   Cause: After investigation we can confirm that the distributor database is with sync with backup option. And that cause the issue   Resolution: At this end to solve the issue, I remove this option that we don’t need. I also check this property to all…

1

Command sp_cycle_agent_errorlog is failing

    Problem description: on ours SQL Server 2008, when we execute “EXECUTE msdb.[dbo].[sp_cycle_agent_errorlog] “, we got the error message below:     Msg 22022, Level 16, State 1, Line 0    SQLServerAgent Error: 32. Work done:   Step1: We can see that the log is recycled. The file SQLAGENT.OUT contains for each execution the message below:   …

0

How to create a dependency between two or more Availability Groups

Hi all,   Problem description: I got a specific scenario where I have to failover two or more AlwaysOn Availability Groups in the same time.  To explain by another way, I have to create a dependency between 2 Availability Groups. If one of them failover, the second one has to move also on the same…

1

How configure correctly AlwaysOn readable secondary replica for applicationIntent

  Hi all,   I would like to share with you an issue that I got recently because  I didn’t set  up correctly AlwaysOn to enable readable database on the secondary replica.   Problem description: When I am trying to connect to my application with .Net or PowerShell, I got the following issue only when I…

1

Keyword not supported: 'applicationintent'

  Problem description: When you try to connect to  your SQL Server by using powershell, .Net, sqlcmd… you got this error message: System.ArgumentException: Keyword not supported: ‘applicationintent’.   at System.Data.SqlClient.SqlConnectionStringBuilder.set_Item(String keyword, Object value)   at System.Data.Common.DbConnectionStringBuilder.set_ConnectionString(String value)   Cause: The message occurs when you include ApplicationIntent=ReadOnly (AlwaysOn Availability Groups properties) in your connection string. And  the server…

0

8624 Internal Query Processor Error: The query processor could not produce a query plan

  Problem description: We got some mini memory dump. In side our SQL error log, we can see the error message below           Stack Signature for the dump is 0x00000000950A8E26          External dump process return code 0x20000001.          External dump process returned no errors.Error: 8624, Severity: 16, State: 116.          Internal Query Processor Error: The query processor could…

0

Migration de SQL Server 2000 vers SQL Server 2012

Vous ne pouvez pas migrer directement de SQL server 2000 vers SQL Server 2012. La migration de SQL server 2000 vers 2012 requière une étape intermèdiaire. SQL Server 2012 supporte une mise à jours uniquement depuis uniquement les versions suivantes :  SQL 2005 SP4 ou SQL 2008 SP2 ou SQL 2008 R2 SP1. Si vous essayez de restaurer…

0

Migración de SQL Server 2000 a SQL Server 2012

No se puede migrar directamente a SQL Server 2000 a SQL Server 2012. La migración de SQL Server 2000 a 2012 requiere un paso intermedio. SQL Server 2012 soporta  sólo los versiones siguiente: SQL 2005 SP4 o SQL 2008 SP2 o SQL 2008 R2 SP1. Si intenta restaurar una copia de seguridad de SQL Server 2000, obtendrá el número…

0

Migration SQL Server 2000 to SQL Server 2012

You will be not able to migrate from SQL 2000 to 2012 directly. Migration from 2000 to 2012 requires an intermediate step. SQL Server 2012 supports upgrade from only the following versions: SQL 2005 SP4 or SQL 2008 SP2 or SQL 2008 R2 SP1. If you try to restore a backup database from SQL Server 2000,…

0

¿Qué está el Parameter Sniffing ?

¿Qué está el Parameter Sniffing ? No tenga miedo del “parameter sniffing”. Este es un comportamiento normal del motor. Cuando un procedimiento almacenado se compila o se vuelve a compilar, los valores de los parámetros se “olió” y se utiliza para la estimación de cardinalidad. El plan se optimiza con estos valores de los parámetros como…

0