sql server 2000 tools

13 Dec 2005 9:50 PM

Wendy Elizabeth

My company as a sql server 2000 transaction log file that is too big. I need
to truncate the size of the log file.

I am relatively new to a small company that does not have an assigned DBA
since there are only 5 programmers. I have been working with sql server 2000
for about 6 months. I have been told by my company that I will be performing
the DBA functions.

I am trying to figure out what I need to do to truncate the transaction log
table. I have been setup as the SA for the production data base using
enterprise manager.
I do not individually have access to the production sql server database
except through the SQL Server tools like enterprise manager. Is there a
reason why I would need direct access to the *.ldf file except through
enterprise manager? Do I need to be able to map to the production sql server?
If so, why would I need to setup this link?

Note: I have read the "shrinking and truncating the transaction log" with
the online
help.

Can you recommend to me the best way to truncate and shrink a transaction
log that is too large?

14 Dec 2005 6:36 AM

Danijel Novak

Hi,

First you need to register production server with your username and password
in Enterprise Manager you're using. You don't need to access *.ldf files
directly.
Then you should do a Transaction Log backup from Enterprise Manager.
After backup you can shrink the log also from Enterprise Manager or you can
use DBCC SHRINKFILE.

--
Danijel Novak

Show quote

"Wendy Elizabeth" <WendyElizab***@discussions.microsoft.com> wrote in
message news:1BD9A84F-B5E0-4C50-9327-1D8D047C8C53@microsoft.com...
> My company as a sql server 2000 transaction log file that is too big. I
> need
> to truncate the size of the log file.
>
> I am relatively new to a small company that does not have an assigned DBA
> since there are only 5 programmers. I have been working with sql server
> 2000
> for about 6 months. I have been told by my company that I will be
> performing
> the DBA functions.
>
> I am trying to figure out what I need to do to truncate the transaction
> log
> table. I have been setup as the SA for the production data base using
> enterprise manager.
> I do not individually have access to the production sql server database
> except through the SQL Server tools like enterprise manager. Is there a
> reason why I would need direct access to the *.ldf file except through
> enterprise manager? Do I need to be able to map to the production sql
> server?
> If so, why would I need to setup this link?
>
> Note: I have read the "shrinking and truncating the transaction log" with
> the online
> help.
>
> Can you recommend to me the best way to truncate and shrink a transaction
> log that is too large?