April 9, 2007 at 12:02 pm
Hi
I tried to post a second ago but it asked me to download some control BS so if this is a double post, please excuse.
The problem is that several of us have gone into enterprise manager, selected a table, attempted to design and add a new column to said table and recieve this error when saving:
'tblBob' table
- Unable to modify table.
profile name is not valid
I believe we all have at least dbo permissions, some possibly admin. I also tried giving explicit permissions to this object but still no dice.
(I have not tried an alter table statement yet.)
Any help would be appreceated.
Thanks
April 10, 2007 at 6:41 am
That sounds odd. That's a database mail error. According to BOL either the profile specified doesn't exist or the user running doesn't have permission to access the profile. You may have a DDL trigger in place for auditing or something.
Try this. Go into the SSMS as usual, modify the table, then, instead of saving, get it to generate a script of the changes it was going to make. This way you can see what it's trying to do. You can post that here.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 10, 2007 at 7:14 am
How do I get it to "generate a script of the changes it was going to make?" I seem to only have a save error file option.
April 10, 2007 at 8:18 am
By default there's a button that looks like a scroll with a disk in front of it that is "Generate Change Script." Clicking on that button will show the script that SSMS is generating for the change. If the button is missing, right click on the table definition that you're editing and you should see a menu choice "Generate Change Script." You should also have a menu choice called "Table Designer." This too has "Generate Change Script" as a choice. Lots of ways to skin the cat.
I still suspect that someone has set up a DDL trigger on the database. These fire based on CREATE, ALTER & DROP statemenmts. Since you guys are getting an email error when you try to save a table (not exactly normal), then I suspect that's the issue. You might try looking in the database under "Programmability - Database Triggers" to see what's there.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 10, 2007 at 8:21 am
Thanks!
I will look at all those places.
**Edit - one of our guys deleted and recreated it before the soultion was found (probably happen again )**
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy