Database File Restricted

Question

Post reply

Database File Restricted

AndrewSQLDBA

SSC-Insane

Points: 21827
More actions
March 4, 2008 at 3:12 pm

#121048

Hello Everyone
I am having an issue with one of my databases. This is a database that came from a vendor in a canned package.
The database log file is set to a restricted growth size. I have tried changing it to unrestricted, but it will not save that. I need to get the size higher and the percentage of growth lower. I cannot save these changes once I select the "OK" button. It goes back to the original settings of "Restricted"
Had anyone ran across this before? How can I over come this fact and get around this. I need to be able to modify that setting.
Thanks
Andrew SQLDBA

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Vivien Xing SSChampion Points: 12297 More actions · Answer 1

You may need to ask the vendor why and how to. They may set it this way for a reason.

Vivien Xing SSChampion Points: 12297 More actions · Answer 2

You may need to ask the vendor why and how to. They may set it this way for a reason.

AndrewSQLDBA SSC-Insane Points: 21827 More actions · Answer 3

They said they do not know. There are actually 7 databases that support this one app. None of the others have this problem. I can modify that setting on all the others.

Thanks

Andrew SQLDBA

Vivien Xing SSChampion Points: 12297 More actions · Answer 4

How about script the change out and run from Query instead of SSMS?

Alter database [dbname] ... /* one change only each time */

AndrewSQLDBA SSC-Insane Points: 21827 More actions · Answer 5

That is fine, but do I change? I cannot go thru everything about that database making modifications.

Thanks

Andrew SQLDBA

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 6

Andrew - I wouldn't go hog-wild and start changing everything - but I would definitely ask them if you can change that particular setting. I can't imagine how that would screw anything else up, but - better safe than sorry. It seems very strange that they would have put that in that way (it actually seems to be a default setting - I wonder if they just screwed up and forgot about it).

I've seen enough train-wrecks being packaged as third-party commercially licensed products that I'm not at all hesitant to go through and look for settings I find strange. If I find some - I write them down, and set up some time to talk with their support team to find out why they thought a particular setting would be the "right" one. More often than not - it came down to - "well we had to pick something, so we did" and changing it wasn't an issue.

Otherwise - schedule lots of log backups.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

AndrewSQLDBA SSC-Insane Points: 21827 More actions · Answer 7

Thanks for your input on this. Do you know what table that I can query to see the settings? I would like to try and see what some of the other databases on that same box have for this setting. I am thinking that I can modify it that way. The other way is not working.

Thanks

Andrew SQLDBA

Vivien Xing SSChampion Points: 12297 More actions · Answer 8

Take a look books online: System Views (Transact-SQL) > Catalog Views (Transact-SQL).

These 2 may help: sys.database_files and sys.master_files

May have a copy of the database to figure out why instead of modifying directly on the live database.