The lesson learned from this? If you're getting this error about an object in your database, and you're not sure what's generating it, you need to check ALL objects in your database (stored procedures, triggers, etc) to see if you haven't given a complete name for another object (i.e., schema.objectname). Third, specify the name of the table that the trigger is associated with after the ON keyword. Second, use BEFORE INSERT clause to specify the time to invoke the trigger.
The solution was to work with the customer to address the improper reference to the table in the trigger, by either modifying the trigger, or deleting it so the customer could readd the trigger with the proper table reference. First, specify the name of the trigger that you want to create in the CREATE TRIGGER clause. And apparently, during DB user creation, MSSQL 2005 checks through all of this BEFORE it allows the user to be created. and in the trigger was SQL referring to the table as "SecurityLog", not "service.SecurityLog". But why was it causing an error when we tried to add a db user? Because the customer ALSO had a Trigger. The customer had a table named "SecurityLog" created in schema "service". When trying to add a new DB user for a customer, we received the error "Invalid Object Name: SecurityLog". This can show up not ONLY when executing SQL statements, but may even affect you when adding a db user. but if your tableCustomers was created in schema "admin", then you need to specify by the name "admin.tableCustomers". AFTER INSERT It indicates that the trigger will fire after the INSERT operation is executed.
If you specify just "tableCustomers", then dbo.TableCustomers is assumed. The syntax to create an AFTER INSERT Trigger in MySQL is: CREATE TRIGGER triggername AFTER INSERT ON tablename FOR EACH ROW BEGIN - variable declarations - trigger code END Parameters or Arguments triggername The name of the trigger to create. For example, rather than "tableCustomers" you specify "admin.tableCustomers" where "admin" is schema name in which table "tableCustomers" was created. That is why you have to explicitly specify schema name in TableName property if you use SQL Server 2005. In SQL Server 2005, schemas exist independently of the database user that creates them". Every database user is the owner of a schema that has the same name as the user. MSDN says: "In SQL Server 2000, database users and schemas are implicitly connected.
Or, the table exists, but you didn't reference it correctly. MySQL WorkBench - A unified visual tool for database.
you've referenced an object (table, trigger, stored procedure,etc) that doesn't actually exist (i.e., you executed a query to update a table, and that table doesn't exist). Microsoft SQL Server Management Studio - An integrated environment for managing any SQL infrastructure. When starting SQL Server Management Studio 17 DB2 SQL Error: SQLCODE-805. You receive "Invalid object name" when attempting to execute a SQL query or add a new database user to your MSSQL database. Save the settings, quite MySQL Workbench and reopen the connection. Knowledge Essentials - 3Essentials Hosting ERROR: "Invalid object name"