Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 Other Forums
 SQL Server 6.5 \ SQL Server 7.0
 SQL Server 7.0

Author  Topic 

agiotti
Starting Member

37 Posts

Posted - 2010-01-28 : 17:46:45
Don't Yell! This is a vendor application and still running under SQL Server 7.0. They are currently worknig on development to bring it up to the 21st century.

with all the said, I have a very strange issue with one database on this server. Every time a transaction log backup is executed and the inactive portion is backed up successfuly, the transaction log file shrinks.

Same server, another database, that I just created to test with, has all the same settings, the transaction log file does not shrink. when I say shrink I am not talking about the inactive portion of the log, I really mean the physical file.

The data file does not shrink, hence the autoshrink being disabled.

Anyone seen this this before?

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-01-28 : 20:10:05
There's got to be a job scheduled that is causing this. Check all places where SQL jobs can be executed, such as the Agent and Task Scheduler.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

agiotti
Starting Member

37 Posts

Posted - 2010-01-29 : 08:59:24
Hello Tara,
I promise you that I have looked at everything. I actually ran performance monitor and captured the SQL Server: Database: Logsize counter. Ran the BACKUP LOG <DatabaseName> WITH NOINIT and watched the log size shrink. I know this is very strange and cannot put my finger on the cause.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-01-29 : 15:12:41
Run SQL Profiler to see what is going on.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

agiotti
Starting Member

37 Posts

Posted - 2010-01-29 : 23:06:56
I have executed profiler and the only command that was running was BACKUP LOG. I have never seen this before.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-01-30 : 18:16:32
Perhaps it's a bug. Are you running sp4?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-01-31 : 04:50:47
SELECT @@version list link below, if that helps!

http://www.sqlteam.com/article/sql-server-versions
Go to Top of Page

agiotti
Starting Member

37 Posts

Posted - 2010-01-31 : 10:26:27
tkizer: Yes I am running sp4. The strange thing it only happens with this one particular database. No worries, everyone, we are getting of this old platform soon. I just needed to satisfy my curiosity on why this is happening. I was hoping that someone out in the field may have seen the same strange behavior.
Go to Top of Page
   

- Advertisement -