The postings on this site are my own and do not represent my Employer's positions, advice or strategies.


  Wednesday, October 23, 2019


bob tech
Contact Bob
VW Buses
Cook Book


EJ Ironman 2

  bob Links
Navy Federal Credit ...
They who have drunk beer…fall on their back…but there is peculiarity in the effects of the drink made from barley…for they that get drunk on other intoxicating liquors fall on all parts of their body, they fall on the left side, on the right side, on their faces, and on their backs. But it is only those who get drunk on beer that fall on their backs with their faces upward. - Aristotle
Wider View Insert

IBM - AS400
Performance Counters
Service Broker
SQL Server
     Temporary Database
     SQL Mail
     DTS - Data Transformation Services
     Jobs SQL Agent
     User Management
     System Databases
     Temp Tables
     Find the physical se...
     Enable xp_cmdshell
     Intermittent Connect...
     Connection String Pr...
     Login Error ( State)...
     Turn Default Tracing...
     Re-index fails when ...
     Tracing of Errors
     Extra carriage Retur...
     Query to find Object...
     Named Instance Port ...
     Adding Domain Login ...
     Rename Logical File ...
     Error 3624 Delete st...
     SQL DMO Error 21776
     SQL Server Service m...
     Trace Flags for Dead...
     Change Server Name
     Alternate to Count(*...
Windows OS

Insert Category

Will be added as a sub-category of, SQL Server
SQL DMO Error 21776
KB Article - 239133 SYMPTOMS When you run SQL Server Enterprise Manager wizards against objects owned by anyone other than yourself or the database owner (DBO), you may receive errors and the wizard may not complete successfully. Error 21776: [SQL-DMO] The name 'XXXX' was not found in the Users collection. CAUSE The Enterprise Manager does not allow you to specify an owner. So, if you are not logged on as the object owner and the object is not owned by the DBO, the wizards will not find the object. WORKAROUND Use sp_changeobjectowner to change the owner of the table to the DBO, and then run the wizard again. Also see articles: KB 218172