instead, the customer should have created a customer SQL login (for example 'cognos') and given it DBOWNER rights to the database(s).

This is not a recommended method of using SQL logins.

(2) or customer using a custom (created) SQL login (for example 'cognos') but has mistakenly given this 'sysadmin' rights (1) customer using the built-in SQL login 'sa' In other words, customer is using a ('sysadmin') SQL login user (most often the built-in 'sa' account), rather than using the recommended settings which is a 'standard' SQL user (which is then granted dbowner rights).ДЇor example, the problem will affect both the following two separate scenarios:

Scenario #1 (RARE) - Customer using SQL 2000, and is using a 'system administrator' ( SA) account.

There are several scenarios where this occurs:

In other words, all the tables (inside 'SQL Server Management Studio' are preceded by the name ' dbo' (see below):.

(SQLSTATE=42S02, SQLERRORCODE=208)RQP-DEF-0149 The query specification is incorrect.RQP-DEF-0457 Referenced Query 'QuerењњonnectedUsers' is not defined or its query items contain unresolved references.RSV-SRV-0042 Trace back.Д¬ontroller database tables are owned by ' dbo'.

(SQLSTATE=42000, SQLERRORCODE=8180)UDA-SQL-0564 Invalid object name 'cognos.crdConnectedUsersSub'. UDA-SQL-0115 Inappropriate SQL request.UDA-SQL-0564 Deferred prepare could not be completed.UDA-SQL-0564 Statement(s) could not be prepared. X An error occurred while performing operation 'sqlPrepareWithOptions' status='-56'. User Rights and Security Group Reports (Preview) Д«elow is the error seen (when you tick ' Menu Groups'): The problem is seen if the user ticks the option ' Menu Groups' inside 'User Rights and Security Group Reports': In addition, it only affects some selections inside those standard reports.

The problem only affects some (very few) standard reports.

Backup a databse using sql studio 017