Can''t change the Auto growth option on my Database

I'm currently using SQL Server 2005. Before I have set my database on unrestricted auto growth. But today, I have noticed that the Log file has been set to limit its growth to 2,097,152 MB. I have 160GB space for my log files, I just want to maximize the space for logs in my hard drive.

When I try to change the settings back to auto growth it still keeps on returning to its previous setting it is still set on 2,097,152 MB. What I did was :

Right Click on the Database - Properties - Files - Click the (...) - set the auto growth option to unrestricted - Click Ok

But when I checked log file, it is still set on 2,097,152MB.

Can some one help me change the settings of my Database.

I think its the maximum to which the log file can grow i.e upto 2 TB refer,

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=175549

even if you set it as unlimited it reverts to 2 TB i guess....it seems to be a bug with sp1 and is closed by design, even if you alter the filegrowth through scripts it doesnt revert

|||

Is there any querry / command that I can use to set the auto growth option on my log files? my real problem was giving the log files a different settings. My database was running for almost 1 year now. This is the first time that I saw this kind of error, well actually it doesnt return any error. It just doesn't accept the settings that I gave.

Having 160GB of Hard Disk space and my log file is being limited to just 2GB is very frustraiting (lol) Hope you guys can give me some ideas.

|||

the query is available in my previous post (link) i gave and they have clearly showed that you cannot change the settings through query either........go for SP2 but i am not sure it will yield the desired results....it was a bug with sp1

|||

But you aren't limited to 2 GB. You are limited to 2 TB.

2,097,152 MB = 2 TB (not 2 GB).

If you were trying to set it to a size greater than 2,097,152 MB, it wasn't an allowable value as you would have been trying to exceed the 2 GB max for a transaction log size.

-Sue

|||

If it is set to 2TB then why doest it now allow me to make any changes on my data? Sorry for the nooby questions and mistakes. I just dont want anything bad to happen on my database.

What are the solutions that I can make to change it back to normal?

|||

No problem on the noob questions...everyone starts there at some point.

Going back to your problem, what you really want to do is give some details on what the problem really is - all we have to go on is the auto growth and file size issue but in this post you said you can't make any changes to your data. Could you give us a step by step example of what issues you are running into, what the exact error number and messages are?

Thanks,

-Sue

Cant Auto-Start Agent

I have a SQL Server 2000 that failed to start after a Windows reboot.
Agent properties are checked to auto start if stopped. Under the Agent
Error Log, I have the following data:

Information:
SQL Agent stopping because of Windows shutdown.
SQL Agent terminated normally.

Error:
SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.
Logon to server(local) failed.

Help apprecaited. Thanks
Frank

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Frank Py <fpy@.proactnet.com> wrote in message news:<3f843998$0$202$75868355@.news.frii.net>...
> I have a SQL Server 2000 that failed to start after a Windows reboot.
> Agent properties are checked to auto start if stopped. Under the Agent
> Error Log, I have the following data:
> Information:
> SQL Agent stopping because of Windows shutdown.
> SQL Agent terminated normally.
> Error:
> SQL Server Error: 1115, cannot generate SSPI context SQLState HY000.
> Logon to server(local) failed.
> Help apprecaited. Thanks
> Frank
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

You might find these KB articles helpful:

http://support.microsoft.com/defaul...9&Product=sql2k
http://support.microsoft.com/defaul...4&Product=sql2k

Simon|||I am having this problem, too. Have you found a solution?

Cannot sync when Auto Identity Ranges Enabled?

I have been pulling my hair out with this for some time now:
I have a small db which I need to merge replicate with a number of PocketPC
devices. NT Authentication is used.
If I do not enable the automatic identity range option, the PocketPC clients
can connect without error. However, if I enable this (which I need to), the
PocketPC user gets a host of errors:
1. (Code 80004005) A call to SQL Server Reconciler failed.
2. (Code 80045007) The merge process could not retrieve article information
for publication 'Survey'
3. (Code 0) {call sp_MShelpmergearticles(?,8000000,?)}
4. (Code 4833) Could not connect to server 'SERVER1' because 'SQLAdmin' is
not defined as a remote login at the server.
SQLAdmin is our Service startup account. It is a member of the Administrator
group.
The user account being used to connect is a standard domain user account.
If I add the user to the Administrators group the process succeeds
everytime. I have checked permissions on the SQLCE folder, and snapshot
folders and AFAIK they are correct (i.e. the user has write permission).
It looks like a permission problem, but I dont know where. It seems the only
solution to this is to add the user to the Administrators group (totally
unacceptable!).
Any suggestions because I am at a complete loss?
Cheers,
James Goodman
Did you re-run your merge agent? I've had no problem using a domain user
account, particularly if set up for anonymous subscribers. Also, you should
be getting a 280xx error number back from the errors collection in the .Net
code. The MSDN site has a list that precisely defines what each of those
errors mean.
"James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
news:ufn1ZWObFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have been pulling my hair out with this for some time now:
> I have a small db which I need to merge replicate with a number of
> PocketPC devices. NT Authentication is used.
> If I do not enable the automatic identity range option, the PocketPC
> clients can connect without error. However, if I enable this (which I need
> to), the PocketPC user gets a host of errors:
> 1. (Code 80004005) A call to SQL Server Reconciler failed.
> 2. (Code 80045007) The merge process could not retrieve article
> information for publication 'Survey'
> 3. (Code 0) {call sp_MShelpmergearticles(?,8000000,?)}
> 4. (Code 4833) Could not connect to server 'SERVER1' because 'SQLAdmin' is
> not defined as a remote login at the server.
> SQLAdmin is our Service startup account. It is a member of the
> Administrator group.
> The user account being used to connect is a standard domain user account.
>
> If I add the user to the Administrators group the process succeeds
> everytime. I have checked permissions on the SQLCE folder, and snapshot
> folders and AFAIK they are correct (i.e. the user has write permission).
> It looks like a permission problem, but I dont know where. It seems the
> only solution to this is to add the user to the Administrators group
> (totally unacceptable!).
>
> Any suggestions because I am at a complete loss?
> --
> Cheers,
> James Goodman
>