Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / July 2008

Tip: Looking for answers? Try searching our database.

Two issues with SQL Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
gamer2k4@gmail.com - 31 Jul 2008 17:14 GMT
My first problem is one that has come up before, but I have yet to see
a suitable (read: one that fixes the problem for me) answer to it.
When I try to increase the size of one of my databases, I get the
following error:

"MODIFY FILE encountered operating system error 112 (There is not
enough space on the disk.) while attempting to expand the physical
file. (Microsoft SQL Server, Error: 5149)"

Like everyone else who's encountered this error, I KNOW that I have
enough space.  The database is under 300MB.  I'm trying to change its
initial size to 500MB.  I have over 50GB of free space on the drive,
and 3GB of RAM (of which at any given time, at least 2GB is free).
I've tried turning off disk quotas, tried giving the user sql full
access, tried turning on auto-expand, and a few other things too I
think, yet the problem remains.  How can I not have enough memory to
expand the file to 500MB?!? Does SQL have only a certain amount of
memory allocated to it? Is the database size dependent on more than
just free hard drive space?

Second problem: SQL is EXTREMELY resource-intensive.  The process
sqlservr.exe (occasionally in conjunction with AutoApprove.exe, which
I have no idea what it is) will regularly take up 100% of my CPU, and
often more than a gigabyte of RAM.  We're not explicitly running any
queries; in fact, most of the time, SQL is just in the background,
with no external influences (that I know of).  So what's causing this
problem?

Thanks in advance for your help.
Aaron Bertrand [SQL Server MVP] - 31 Jul 2008 17:21 GMT
Well, can you create a NEW database that is 500MB?  Or is this problem
isolated to this particular database?

Do you see anything interesting in the event log?

Are you running Small Business Server?  What version?  Have you applied any
updates?

On 7/31/08 12:14 PM, in article
815a7ace-8bc9-4044-b1a0-52af4d7ac14d@f63g2000hsf.googlegroups.com,

> My first problem is one that has come up before, but I have yet to see
> a suitable (read: one that fixes the problem for me) answer to it.
[quoted text clipped - 25 lines]
>
> Thanks in advance for your help.
gamer2k4@gmail.com - 31 Jul 2008 17:34 GMT
On Jul 31, 11:21 am, "Aaron Bertrand [SQL Server MVP]"
<ten....@dnartreb.noraa> wrote:
> Well, can you create a NEW database that is 500MB?  Or is this problem
> isolated to this particular database?

Can't create a new database that big.

> Do you see anything interesting in the event log?

Although I'm not too familiar with the event log, the only thing that
looks relevant is just the "error 112: not enough space" event, which
I already knew about.

> Are you running Small Business Server?  What version?  Have you applied any
> updates?

Yes, Windows Small Business Server 2003 SP2.
Aaron Bertrand [SQL Server MVP] - 31 Jul 2008 17:59 GMT
> Can't create a new database that big.

Meaning you get the same error, or there is not enough space?  If the
latter, you just told us you had 50GB free...

If you get the same error, then it's time to talk to your hardware folks.
This may be a physical disk error that is disguised in the way Windows
reports it back to SQL Server (or how SQL Server interprets it for you).

A
gamer2k4@gmail.com - 31 Jul 2008 19:27 GMT
On Jul 31, 11:59 am, "Aaron Bertrand [SQL Server MVP]"
<ten....@dnartreb.noraa> wrote:
> > Can't create a new database that big.
>
> Meaning you get the same error, or there is not enough space?  If the
> latter, you just told us you had 50GB free...

Meaning I get the same error.

> If you get the same error, then it's time to talk to your hardware folks.
> This may be a physical disk error that is disguised in the way Windows
> reports it back to SQL Server (or how SQL Server interprets it for you).

Wouldn't the ability to download or install or otherwise add other
large files kind of refute that? In other words, if I can't increase
the size of the database by 200MB, but I can download and install a
300MB service pack, then that can't be the issue, right?

Seems to me the only other option (for the physical disk error, that
is) would be that the area where that particular database is has some
bad sectors shortly after the end of the database.  Wouldn't the new
database be in a completely different part of memory?
gamer2k4@gmail.com - 31 Jul 2008 19:35 GMT
On Jul 31, 1:27 pm, gamer...@gmail.com wrote:
> On Jul 31, 11:59 am, "Aaron Bertrand [SQL Server MVP]"
>
[quoted text clipped - 5 lines]
>
> Meaning I get the same error.

On the other hand, I CAN alter certain other pre-existing databases to
have more space allocated to them.  Perhaps I could just try deleting
the database and starting over? (It's a database for MS BCM that we're
using to import a list of contacts; nothing vital is in it right now.)
Chris Wood - 31 Jul 2008 17:24 GMT
can you provide some details of your SQL installation? Is this SQL2000 or
SQL2005 or even MSDE2000 and what build and on what version/level of
Windows?

Chris

> My first problem is one that has come up before, but I have yet to see
> a suitable (read: one that fixes the problem for me) answer to it.
[quoted text clipped - 25 lines]
>
> Thanks in advance for your help.
gamer2k4@gmail.com - 31 Jul 2008 17:43 GMT
> can you provide some details of your SQL installation? Is this SQL2000 or
> SQL2005 or even MSDE2000 and what build and on what version/level of
> Windows?

Oh...right.  I suppose that would have been useful.  I'm running SQL
Server 2005 SP2.  Here's the relevant info from the About screen in
SQL Server Management Studio:

Microsoft SQL Server Management Studio    9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC)    2000.086.3959.00
(srv03_sp2_rtm.070216-1710)
Microsoft MSXML                2.6 3.0 4.0 6.0
Microsoft Internet Explorer        7.0.5730.13
Microsoft .NET Framework        2.0.50727.1433
Operating System            5.2.3790

At least, I THINK that's relevant.
Aaron Bertrand [SQL Server MVP] - 31 Jul 2008 18:00 GMT
Nah, management studio Help|About just tells you information about the
client application.  Better to run SELECT @@VERSION from a query window
against the server.

On 7/31/08 12:43 PM, in article
5f32a5b1-e1ac-410a-952c-349de693f3c0@34g2000hsf.googlegroups.com,

>> can you provide some details of your SQL installation? Is this SQL2000 or
>> SQL2005 or even MSDE2000 and what build and on what version/level of
[quoted text clipped - 14 lines]
>
> At least, I THINK that's relevant.
gamer2k4@gmail.com - 31 Jul 2008 19:24 GMT
On Jul 31, 12:00 pm, "Aaron Bertrand [SQL Server MVP]"
<ten....@dnartreb.noraa> wrote:
> Nah, management studio Help|About just tells you information about the
> client application.  Better to run SELECT @@VERSION from a query window
> against the server.

Microsoft SQL Server 2005 - 9.00.3233.00 (Intel X86)   Mar  6 2008
22:09:47   Copyright (c) 1988-2005 Microsoft Corporation  Workgroup
Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Roy Harvey (SQL Server MVP) - 31 Jul 2008 20:58 GMT
A low probability idea out of left field....  

Is there any sort of "disk quota" software running on the server?  The
kind intended to keep a user from using more than their share of disk
space?  I suppose if the account under which the SQL Server service
was running had a limit....

As I said, out of left field.

Roy  Harvey
Beacon Falls, CT
gamer2k4@gmail.com - 31 Jul 2008 21:08 GMT
On Jul 31, 2:58 pm, "Roy Harvey (SQL Server MVP)"
<roy_har...@snet.net> wrote:
> A low probability idea out of left field....  
>
> Is there any sort of "disk quota" software running on the server?  The
> kind intended to keep a user from using more than their share of disk
> space?  I suppose if the account under which the SQL Server service
> was running had a limit....

There was a quota, but it was 1GB (still more than the database
required but probably less than the total size of all the databases).
However, I turned it off as one of the attempts to fix the problem, to
no avail.
TheSQLGuru - 01 Aug 2008 00:16 GMT
For the second issue, if this is a web-facing application database I would
check to see if you are getting hit by the worm that updates all text fields
and appends <script... to the end of each value.

Signature

Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net

> My first problem is one that has come up before, but I have yet to see
> a suitable (read: one that fixes the problem for me) answer to it.
[quoted text clipped - 25 lines]
>
> Thanks in advance for your help.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.