RE: SMS 2003 SP2 and SQL 2000

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Correction to my comment near the end, I DO NOT know much about SQL server.

"daflip" wrote:

This questions is not directly towards SMS but more so towards SQL. I am
hoping someone here can help since our SMS site server is using SQL for
database management. Furhtermore, it does have something to do with SMS's
database in SQL.

Over the past few months, a collegue of mine and myself have noticed that
hard drive space is running out on our SMS server. This server also has the
install files of different software (as well as software updates and patches)
that were deployed using SMS. SQL is also installed on this server.

We have been deleting or moving old folders/directories to free up space but
after the next day, most of that free space has been used. We noticed a
folder named "<servername> SQL Backup". In this folder it has several
subfolders which I assume SQL created including defaults such as Master,
Model, MSDB. The other one is the named after the SMS site server name (for
example - SMS_Site01). After checking it out, SMS_Site01 has a file that is
extremely large with no known extension for it. Last week it was
approximately 830GB large. My collegue freed some space over the past
weekend and now the files has grown to a little over 900GB). Most of the
free space that was allocated over the weekend was immediately used up.

We believe that this backup folder for SQL is directly responsible for the
diminishing hard drive space on the SMS server.

We both do not know much about SQL server. The responsibility of the SMS
server was handed down to me after the secondary admin left (primary left a
couple of years ago). Anyways, my collegue herself does not know much of SQL
either. We were able to go into the SQL server manager and checked the
database instance for the SMS server. We noticed that the backups of the SQL
database for SMS occurs daily in the afternoon. Is this frequency too much?
Should it only be backed up once a week or maybe once a month?

Also, is there a way better way to manage the SQL database for SMS so it
does not get extremely large. Perhaps a way to compact the database? Again,
I must stress that I know much about SQL server.

I am hoping that someone here can help. I am also going to post this
question in a SQL newsgroup, if there is any.

Thanks in advance to anyone who can help.
.

Relevant Pages

  • RE: Backups have Shadow Copy Problems
    ... and restarted the server. ... suggested and changed the recovery model to simple on the one database called ... I understand the issue to be: the backup task failed ... You back up data from a volume that contains a Microsoft SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: upsizing to sql 2005
    ... the word SERVER in it, ... You can access to the database by multiple means (Access, ... and how does it update the SQL database with the new records in Access? ... Query Name: Arcadia - ARC ...
    (microsoft.public.access.queries)
  • Moving SMS SQL Database
    ... We have a customer running SMS 2003 in Advanced Security with a remote SMS SQL database. ... They need us to move the database to a different server. ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 SP2 and SQL 2000
    ... most likely the issues is related to that you are using "core" SQL functionality to dump the database to the same file every time it back's up the SMS db. ... As Garth did mention you should disable all this SQL Server Agent jobs and rather rely on the SMS_SITE_BACKUP task instead, as it will backup all required components at the same point in time. ...
    (microsoft.public.sms.admin)
  • Re: Linked Tables in Access
    ... any use of SQL Passthru, Linked Tables or any other use of MDB / MDE ... server, or would I also need to convert *those* queries to passthrough ... I've been trying to understand why Access database files become corrupt. ...
    (microsoft.public.access.adp.sqlserver)