i got a prolem with the space of my C drive as the dadta bas eis too big for
it i am not a llowed to get a bigger disk drive but i am given another one
that means i got two small disk drives my data isn't inpputed fully into the
database and the disk drive is full . I check the mdf file and found out tha
t
the mdf file stands a smaller space compared to the ldf file .So i am
thinking of deleting the ldf file to make space or else what should i do? I
really need help .The quick answer is: Read up on Recovery Models, then when you understand
the risk, set the recovery model to simple. This will solve your transaction
log disk space problem but introduce a data recovery problem so you'll want
to make frequent back-ups.
-Paul Nielsen
SQL Server MVP
www.SQLServerBible.com
"Fairy239" <Fairy239@.discussions.microsoft.com> wrote in message
news:39E5ACBA-822E-43CB-BF99-9E8AB374228C@.microsoft.com...
>i got a prolem with the space of my C drive as the dadta bas eis too big
>for
> it i am not a llowed to get a bigger disk drive but i am given another one
> that means i got two small disk drives my data isn't inpputed fully into
> the
> database and the disk drive is full . I check the mdf file and found out
> that
> the mdf file stands a smaller space compared to the ldf file .So i am
> thinking of deleting the ldf file to make space or else what should i do?
> I
> really need help .|||
"Paul Nielsen (MVP)" wrote:
> The quick answer is: Read up on Recovery Models, then when you understand
> the risk, set the recovery model to simple. This will solve your transacti
on
> log disk space problem but introduce a data recovery problem so you'll wan
t
> to make frequent back-ups.
> -Paul Nielsen
> SQL Server MVP
i hope you can answer my qn and not asking me to read up stuff this stuff is
urgent need to besloved quickly i got a limit of time for completing the job
thank you
> www.SQLServerBible.com
>
> "Fairy239" <Fairy239@.discussions.microsoft.com> wrote in message
> news:39E5ACBA-822E-43CB-BF99-9E8AB374228C@.microsoft.com...
>
>|||No, the database can't run without an ldf file. Try moving either the ldf
or mdf file to the new drive - detach the database and then attach with
move. This article show how that works:
http://msdn2.microsoft.com/en-us/library/ms187858.aspx
http://support.microsoft.com/defaul...kb;en-us;818565
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Fairy239" <Fairy239@.discussions.microsoft.com> wrote in message
news:CCB6FE51-B406-4C6B-96BC-5116BDDA9E7E@.microsoft.com...
>
> "Paul Nielsen (MVP)" wrote:
>
> i hope you can answer my qn and not asking me to read up stuff this stuff
> is
> urgent need to besloved quickly i got a limit of time for completing the
> job
> thank you|||to truncate the transaction log try doing :
backup log database_name with truncate_only
then
dbcc shrinklog('Log_File_name')
do remember to take a back up of the db prior to doing this.
also read up the recovery models as stated previously.
Harshal Mistry
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message news:%23qFHtWtVGHA.5012@.TK2M
SFTNGP10.phx.gbl...
> No, the database can't run without an ldf file. Try moving either the ldf
> or mdf file to the new drive - detach the database and then attach with
> move. This article show how that works:
>
> http://msdn2.microsoft.com/en-us/library/ms187858.aspx
> http://support.microsoft.com/defaul...kb;en-us;818565
>
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> "Fairy239" <Fairy239@.discussions.microsoft.com> wrote in message
> news:CCB6FE51-B406-4C6B-96BC-5116BDDA9E7E@.microsoft.com...
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment