So I have another odd question for the group.
We have been running file based replication for a solid 10 years within this one database I'm maintaining. Every time a user replicates from off-site, the last thing we do is copy their individual replication log that we generate each time using the -o and -v switches. We replace it each time on the users machine and copy it to our consolidated log directory. So they only have a copy of their latest log file and it gets replaced each time they run replication.
Now, on the server side, we keep a consolidated log of EVERYTHING that gets replicated up to the consolidated database. It's allowed us to chase down errors that we could then fix via our resolve update triggers. Life was wonderful!!
Uhhh.... That was until our consolidated log file reached the size of 2,051,388KB.
Now I have the wonderful issue that I don't have an editor that will open the log file. So yes, I'm guessing I need to find something that can split this file in half, or shave a chunk off of it, and then save half of it. Save the other half, etc. You get the picture.
So I've tried notepad and notepad++ to open the log file. I'm on a 64bit machine with 8 gig of RAM. No luck.
Anybody aware of any editors that would open a file this big? The replication engine obviously has no problem continuing to append the current content onto the end of the file.
Anywho... Just curious if anybody is aware of an editor that could open up file this large.
Thanks everyone! :)
asked 23 Jun '15, 19:17
Steps to fix the transaction log
For example: F:\Temp>
Type > dbeng50.exe software.db You may need to type in the full path to your dbeng50 executable if sqlany50 is not in your system path. For example: "C:\Program Files\sqlany50\win32\dbeng50.exe" dbfilename.db
Note: This step will start the database server without the transaction log for the first time.
Note: This step will fix the database server.
Note: This step will connect to the database and write a new transaction log.
Note: You can adjust the file so that it no longer uses a transaction log.
answered 17 Jul '15, 03:18
Opens the file a bit at a time and should be good for up to 10GB logs. We have used a similar one for large translated transaction logs, (I know you are talking about replication logs but the principal applies) ;)
EDIT: That one is not as good as I thought.
The one mentioned here: http://www.rizalalmashoor.com/blog/large-text-file-viewer/ (which is the one we used before) does the job beautifully. Unfortunately the website links is no longer operational. I have it though and can put it on a ftp for you if you want it - it's freeware?!?!