SQL 2000 logfiles in EM



  • 1. Upgrade Wizzard
    Hello again This is on a different server from the other question I just posted. I have SQL Server versions 6.5 and 2000 installed on a Windows 2000 server. I installed 6.5 first, coppied a backup of a database to the server and restored it. I then installed 2000. I am trying to use the upgrade wizzard. On the first screen I keep the default settings, export and import objects and data, use a named pipe. Its all on the same server, give it the sa password for both installations (its the same). All services are running under local system account. It switches between the two versions a couple of times then comes up with this error message: Couldn't create or register the SQLUpgrade DSN Anybody got any idea what it means? Regards Matt
  • 2. Missing Program group
    Guys and Girls I have a server that was running SQL Server 2000 (on Windows 2000 server). In preperation for an upgrade from an old SQL Server 6.5 system. I un-installed 2000. I edited the registry to remove all references to SQL Server and deleted all files. I have run an install of 6.5. It seems to have worked all right except there is no program groups on my start menu. Any ideas what might have happened? Regards Matt
  • 3. Performance gain by switching from Win2000 to Win2003?
    Currently have Win2000 Enterprise, 4 Xeon CPU, 4 GB memory. Spec for Win2003 mentions better use of hyperthreading for SQL Server and IO performance. Do you leave hyperthreading on at BIOS level for OS to use but prevent SQL Server from using it by unchecking the last few set of the processors in EM? Can I expect a 5% to 10% perf. increase by upgrading from Win2000 to Win2003? Also thinking about upgrading 4GB to 8GB using /PAE is there a heavy perf. hit by the /PAE addressing? The cache stat on Prepared is at 60%. Thanks.
  • 4. Moving Database Problem (Chinese)
    Here is the setup. I have a SQL Server 7 DB in China that I need to move to a SQL 2000 machine in US. I have tried several different methods, but the Chinese characters are always messed up. I have created the Server/Database with the CHinese_PRC_CI_AS collation, which matches the SQL7 database. I have restored from a backup, and even detached the database from the 7.0 and attached it to the 2000. Same thing. Both servers are English (Win2k & SQL). They have the appropriate Language packs installed. If I open up Enterprise Manager, I can manually type the Chinese characters in through the IME, and they appear correctly, but the ones transferred do not show the correct character. I have looked at the actual Unicode value of the characters in the field and verified that they are all single byte. On the detach/attach, the tech in China detached the database, made a copy and Rar'd it, then FTP to my server. Is it possible that the saving/copying/zipping has affected the data? Any suggestions are greatly appreciated. larry
  • 5. SP4 memory utilization problem
    The configuration is: OS: Windows 2003 Enterprise Edition RAM: 6GB boot.ini switches : /fastdetect /PAE /3GB /USERVA=3030 SQL 2000 Enterprise Edition SP3a (awe enabled; min server memory (MB) = max server memory (MB) = 5120) Before installing SP4 SQL server uses configured amount of memory (5120MB). After installing SP4 it doesn't utilize more than 3GB of memory the SQL Server Logs reports "Warning: unable to allocate 'min server memory' of 5120MB."

SQL 2000 logfiles in EM

Postby Jay » Thu, 06 Sep 2007 03:02:38 GMT

I just noticed that the log files in EM are not rolling on a regular 

I don't know how to change this, but I would prefer them to cycle daily, or 


Re: SQL 2000 logfiles in EM

Postby Tibor Karaszi » Thu, 06 Sep 2007 03:14:33 GMT

You mean the errorlog files? If so it only cycles on SQL Server startup. Check out sp_cycle_errorlog 
(which you can schedule of you wish).

Tibor Karaszi, SQL Server MVP

Re: SQL 2000 logfiles in EM

Postby Jay » Thu, 06 Sep 2007 04:09:41 GMT

Yup, that was it.

My problem was that the current log file was about 500 MB (covering about 7 
months) and pulling it from my workstation caused some issues. I suspect 
mostly from the source server, which is under powered, has a lousy network 
connection and slow and fragmented drives.

So, what is a reasonable time frame for an error log? If you're on top of 
the system, I think once a day, perhaps once a week. No less often than once 
a month though.


"Tibor Karaszi" < XXXX@XXXXX.COM > wrote in 

Re: SQL 2000 logfiles in EM

Postby Tibor Karaszi » Thu, 06 Sep 2007 04:46:18 GMT

> So, what is a reasonable time frame for an error log?

The usual: It depends. :-)

First, you can configure number of history files. Through GUI in EM's 2000. I'm not sure whether 
SSMS exposes this, but I bet you can find it in the registry. If you re-cycle frequently, you 
probably want to have more old files.

Or, you can add up the smartness by each time you cycle, you take the errorlog.1 file and zip it 
into and archive (it zips really well since it is text).

And, if you are really ambitious, do some search (grep(?) or whatever utilities there might be) to 
remove stuff you know you aren't interested in, before you zip it.

Also, since you are concerned with size, why not add a condition for the cycle based on file size?

And in SQL Server 2000, you can control to some extent whether some system messages are written to 
eventlog/errorlog in the first place. See sp_altermessage and the dlevel column in sysmessages.

So, there's much you can do. One thing I do recommend, is to keep a reasonable amount of history for 
these. For instance, the first time a corruption is encountered, SQL Server writes information. Say 
it takes a few days before you discover this (you are on vacation), then you definitely want these 
entries available. And you probably want to back-track to see if there are older things that can 
possibly be the root cause.

Tibor Karaszi, SQL Server MVP

Re: SQL 2000 logfiles in EM

Postby Jay » Thu, 06 Sep 2007 05:01:23 GMT

think once a month and 6 archives is a good starting point. I seriously
doubt I will ever have to go beyond the 1st archive.


"Tibor Karaszi" < XXXX@XXXXX.COM > wrote in
message news:e0$ XXXX@XXXXX.COM ...

Re: SQL 2000 logfiles in EM

Postby Aaron Bertrand [SQL Server MVP] » Thu, 06 Sep 2007 05:07:35 GMT

So if you schedule the log file rollover to happen once a month, you 
shouldn't have to do anything, since SQL Server will keep more than enough 
to meet your 6-month threshold.

However, there is a scenario you may have to pay attention to: manual / 
unplanned restarts.  Say you apply windows updates and/or SQL SPs during a 
maintenance window and restart the service and/or reboot the box multiple 
times, now you just lost a good portion of your archive.  So, you may want 
to have a separate windows scheduled task that archives the files once a 
week and deletes any archives > 6 months old (or whatever your desired 

Re: SQL 2000 logfiles in EM

Postby Aaron Bertrand [SQL Server MVP] » Fri, 07 Sep 2007 00:55:27 GMT

o make this easier, I just spotted Kevin Kline's article in SQL Server Mag,
which points to a download from Microsoft that helps automation tasks like
this. One of the scripts is called "SQLCycleErrorLog" and lets you schedule
the cycling by calling a stored procedure instead of manually creating the
job yourself... see the article here:


And you can get the set of scripts here:


"Jay" < XXXX@XXXXX.COM > wrote in message
news:O% XXXX@XXXXX.COM ...

Similar Threads:

1.Change logfile location durring setup SQL 2000

Is there a possibility to change the default instalation directory for
the logfiles for sql server 2000? I would like the default database
files to be placed on teh d: drive and the logfiles on the e: drive?

Sjaak van Esdonk

2.Cannot truncate logfile in SQL server 2000

Nilkanth Desai

I am using SQL Server 2000. In this case database size is 750 MB and since 
last 10 days its logfile is constantly increasing its size. Since last 2 days 
it has crossed 14GB. Thses logfiles are having extension of .ldf. I have 
tried shrink database option from Enterprise manager and used DBCC from query 
analyser. But this logfile did not truncated. 
      Can anyone tell me solution for this problem.

3.Missing steps when opening a SQL 7 package in SQL 2000 EM


I am trying to make a working SQL 7 DTS export package for exporting
data to ms access, to be run on macines using MSDE 1.0.

In the VB program that I have developed, it looks like if some steps
are missing, which causes errors when executing the package.

I decided to open the SQL 7 package on my SQL 2000 machine.... and I
don't see any create steps in the package.. only copy steps!

What could be wrong, or what I am doing wrong?

Hope, that someone can help me..


4.Commands SQL Server 2000 EM to SQL Server 2005 SSMS

Is there a white paper, website link, or paper that can show me how to 
complete every task that you complete with SQL Server 2000 Enterprise Manager 
the same task with SQL Server 2005 SSMS? (Security,Backup,Maintenance,etc.)

Or the tasks that you completed with SQL Server 2005 SSMS that correspond to 
SQL Server 2000 EM.

Please help me complete this task.


5.SQL Server 2000 EM Register SQL Server W/O GUI

Is there away to register SQL Sever 2000 database server with or without the 
Enterprise Manager GUI with a different Windows user account?

I would like to register approximately 20 servers from a single server but I 
do not have all the sa passwords for the servers.  But I do have the 
different windows user accounts to the servers.

Please help me with this task.

6. SQL 2000 EM Fails in Windows XP

7. Please HELP: SQL 2000 SP3a & EM: Can't register a Server

8. EM crashes on open DTS package for Design - No error - SQL 2000



Who is online

Users browsing this forum: No registered users and 35 guest