Options
object reference not set to an instance of an object
dbdmora
Posts: 50
I am on SQL Compare Pro 10.0.0.143. I am updating my DB with alter permissions only that were commited to SSC and using the deployment Wizard and I get this Error message (object reference not set to an instance of an object) and the wizard won't deploy the script automatically. I copy the script into SSMS and run it, and it works. What am I doing wrong or a bug with software?
/*
Run this script on:
Prodserver1.db1 (Rev. 51526) - This database will be modified
to synchronize it with a database with the schema represented by:
DevServer1.db1 (Rev. 52003)
You are recommended to back up your database before running this script
Script created by SQL Compare version 10.0.0 from Red Gate Software Ltd at 3/2/2012 10:32:14 AM
*/
SET NUMERIC_ROUNDABORT OFF
GO
SET ANSI_PADDING, ANSI_WARNINGS, CONCAT_NULL_YIELDS_NULL, ARITHABORT, QUOTED_IDENTIFIER, ANSI_NULLS ON
GO
PRINT N'Altering permissions on [dbo].[ML_FreeTilMayPromo2]'
GO
GRANT ALTER ON [dbo].[Table1] TO [dbuser1]
GRANT SELECT ON [dbo].[Table1] TO [dbuser1]
GRANT INSERT ON [dbo].[Table1] TO [dbuser1]
GRANT DELETE ON [dbo].[Table1] TO [dbuser1]
GRANT UPDATE ON [dbo].[Table1] TO [dbuser1]
GO
/*
Run this script on:
Prodserver1.db1 (Rev. 51526) - This database will be modified
to synchronize it with a database with the schema represented by:
DevServer1.db1 (Rev. 52003)
You are recommended to back up your database before running this script
Script created by SQL Compare version 10.0.0 from Red Gate Software Ltd at 3/2/2012 10:32:14 AM
*/
SET NUMERIC_ROUNDABORT OFF
GO
SET ANSI_PADDING, ANSI_WARNINGS, CONCAT_NULL_YIELDS_NULL, ARITHABORT, QUOTED_IDENTIFIER, ANSI_NULLS ON
GO
PRINT N'Altering permissions on [dbo].[ML_FreeTilMayPromo2]'
GO
GRANT ALTER ON [dbo].[Table1] TO [dbuser1]
GRANT SELECT ON [dbo].[Table1] TO [dbuser1]
GRANT INSERT ON [dbo].[Table1] TO [dbuser1]
GRANT DELETE ON [dbo].[Table1] TO [dbuser1]
GRANT UPDATE ON [dbo].[Table1] TO [dbuser1]
GO
Comments
It sounds like a bug, but I don't think we know about it. When you encounter this error, do you get a chance to submit the error report (with your email)?