Past week we were using tool for scanning database metadata across all our production servers and at one of them the tool captured following error when trying to access one of the databases: After some searching and investigating detail about the server we captured two core informations: The database is…
SQL Server allows us to create database clone using DBCC CLONEDATABASE command. Cloned database can be then used in SQL Server Management Studio like any other database. But for sure exception exists there: When we will try to browse object contained in cloned database everything works (procedures, functions, ..) until…
Last week we have seen this error when we have initialized new Subscriber from snapshot that was generated for transactional replication after published database schema was updated: ‘An error has occurred: Incorrect syntax near where’ This error occurred after about one hour of applying snapshot to subscribers database and caused…
If you will try to load new data from data source in SSAS tabular project: You can see following error message:
#Errors in SSMS built-in reports
21. 8. 2017
If you see picture like below in SSMS build in reports (Disk Usage by Top Table in this case) don’t get panic: It’s only another funny example of well known Out.Of.Memory exception. Just restart SSMS to get better;).
There is still the same bug many years back starting from SSMS 2005. And yes, it is still not corrected in SSMS 2016. If you will create table where one of the columns has name SEND (keyword in SQL Server) and BIT data type, you are not able to edit…
We have noticed the following error message periodically during mass data update on one of our productions servers: ‘Error 601: Could not continue scan with NOLOCK due to data movement’. This server is hosting instance of SQL Server 2008R2 SP1 Standard edition. After some research we have found a detailed…
We have detected the following issue in production after upgrade from SQL Server 2012 SP2 to SQL Server 2014 SP1 with CU5: ‘Failed to initialize sqlcmd library with error number -2147024809“. This message is fired when we try to send an email using sp_send_mail procedure with the query result to…
Na produkčním serveru se pravidelně při větší update dat začalo objevovat následující chybové hlášení: ‘Error 601: Could not continue scan with NOLOCK due to data movement’. Produkční server běží na SQL Server 2008R2 SP1 Standard edition. Po delší hledání se podařilo najít popis chyby v tomto KB: http://support.microsoft.com/kb/960770/en-us.