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

Moving SSAS Database to a new drive on same server

Problem description: After you moved SSAS databases to a new drive on the same server, you are not able to administrate  Analysis Service. SSAS databases is up and running. When you add a database or user, it appears that users are added successfully, but when going back out of the dialog nothing happened. Work done:…

0

How a clustered instance of Analysis Services works

  Analysis Services is clustered as  a generic service resource on a Windows failover cluster. This applies to 2005, 2008, 2008R2, and 2012.   Since SSAS 2005 version, Analysis Services is fully integrated into clustering Setup (the install of SQL):        – SSAS 2005 cluster setup is adding the service on all cluster nodes on the same…

0

Invoke-Sqlcmd : The 32-bit OLE DB provider "MSOLAP" cannot be loaded in-process on a 64-bit SQL Server

  Problem description : The PowerShell command below uses to run every 5 minutes. But since 2 days, I got the error message below :  Invoke-Sqlcmd : The 32-bit OLE DB provider “MSOLAP” cannot be loaded in-process on a 64-bit SQL Server.  (Invoke-Sqlcmd -ServerInstance $R -Database SSAS_Monitor -Query “INSERT INTO dbo.SSAS_DISCOVER_SESSIONS SELECT  ‘$I’, getdate(), *…

1

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

¿Está de acuerdo en añadir una instancia de SSAS 2012 a un grupo de clúster de SQL Server 2012 existe?

Esto no se admite para agregar o quitar una característica de una instancia de clúster. El asistente de instalación de SQL Server 2012 no permite agregar funcionalidad a una instancia de clúster de SQL Server Failover. Si utiliza el asistente de instalación, recibirá el mensaje de error siguiente:–  Instance name ‘<Instance Name>’ is already in…

0

Est-il pris en charge d’ajouter une instance SSAS 2012 à un group cluster SQL 2012 existant ?

Ce n’est pas supporté d’ajouter ou supprimer une fonctionnalité d’une instance en cluster. L’assistant d’installation de SQL Server  2012 ne supporte pas d’ajouter une fonctionnalité à une instance SQL server en Cluster Failover. Si vous utilisez l’assistant d’installation, vous obtiendrez le message d’erreur suivant:–  Instance name ‘<Instance Name>’ is already in use. To continue, specify a…

0

Is-it supported to add SSAS 2012 instance to an existing SQL 2012 virtual server group ?

How add Analysis Services to a clustered SQL Server instance ? It’s not supported to Add or Remove features for Clustered instances SQL Server setup 2012 does not support adding features to an existing failover cluster instance. By using the wizard, you will get the following error message:–  Instance name ‘<Instance Name>’ is already in…

0