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

LifeAsBob

  Monday, June 18, 2018

 


Home
Blog
bob tech
Calendar
Contact Bob
Pictures
VW Buses
HomeBrew
Cook Book

 

Branson Vacation 2007
  bob Links
Deja.com Re auto-ftp...
I have received delegations of working men who come, apparently speaking of the utmost sincerity, have declared that they would regard it as a genuine hardship to be deprived of their beer. - Woodrow Wilson
Wider View Insert

Cluster
DOS
IBM - AS400
MOM
Performance Counters
Service Broker
SQL Server
     Temporary Database
     Views
     Backup
     SQL Mail
     DTS - Data Transformation Services
     Memory
     Security
     Excel
     Jobs SQL Agent
     MSDE
     Install
     DBCC
     User Management
     System Databases
     BCV
     Deadlocks
     Temp Tables
     Find the physical se...
     Enable xp_cmdshell
     Intermittent Connect...
     Connection String Pr...
     Login Error ( State)...
     Turn Default Tracing...
     Re-index fails when ...
     SMO AND DMO
     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
     NetworkConnections
     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