Archive

Archive for May, 2013

bangalore-user-group-meeting

May 22, 2013 Leave a comment

Hey guys check out cool coverage by Balmukund on bangalore-user-group-meeting

http://sqlserver-help.com/2013/01/22/coverage-report-sql-server-bangalore-user-group-meeting-3-19-january-2013/

banglore_user_group

Enjoy 🙂

 

Categories: General

alter index failed for SCOM OperationsManagerDW

May 22, 2013 Leave a comment

Error :: something similar to below

Executing the query “ALTER INDEX [PK__Performa__AFAD0EB40688E6B3] ON [P…” failed with the following error: “Cannot find index ‘PK__Performa__AFAD0EB40688E6B3’.”.
Executing the query “ALTER INDEX [PK__EventSta__95632343599644AB] ON [E…” failed with the following error: “Cannot find index ‘PK__EventSta__95632343599644AB’.”

 

Cause of error is an in build SCOM functionality that drops and recreates tables named Event Stage (also the associated primary keys) every 60 secs (refer below )

http://blogs.msdn.com/b/sqlserverfaq/archive/2010/04/19/db-maintenance-rebuild-index-task-always-fails-on-operationsmanagerdw-scom-database.aspx

Solution ::

1> you may excluded the database named OperationsManagerDW from re-indexing jobs as this particular DB has its own building maintenance feature that runsEvery 60 secs

http://blogs.technet.com/b/kevinholman/archive/2008/04/12/what-sql-maintenance-should-i-perform-on-my-opsmgr-databases.aspx

enjoy 🙂

An invalid schema or catalog was specified for the provider “SQLNCLI10” for linked server

May 20, 2013 Leave a comment

ERROR: while retrieving data over linked server … you receive below error

Msg 7313, Level 16, State 1, Line 2
An invalid schema or catalog was specified for the provider “SQLNCLI10” for linked server “LinkedServername.DBName .dbo.tablename”

Cause ::

the database named DBName on target server .. that is the server to which your linked server is pointing contains a SPACE in its name

so in reality the database name is   ” DBNAME   ”  that is it has leading or trailing spaces in its name …

steps to resolve the same

1>USE DBNAME;

GO
2> ALTER database DBNAME set single_user with rollback immediate

go

3> EXEC sp_renamedb ‘DBNAME  ‘, ‘DBNAME123

go

4> EXEC sp_renamedb ‘DBNAME123’, ‘DBNAME

above script will resolve the linked server error :

if you try to run below script and by pass step no. 3 .. you will receive an error saying database named DBNAME already exist

EXEC sp_renamedb ‘DBNAME  ‘, ‘DBNAME‘   (SQL need the new name to be different from the old name )

so follow step 1 to 4 .. to resolve error similar to below :: enjoy 🙂

An invalid schema or catalog was specified for the provider “SQLNCLI10” for linked server

 

Categories: linked Server