logical log entries for unlogged db

logical log entries for unlogged db

Post by Doug McAlliste » Sun, 31 Dec 1899 09:00:00



Hi all..

I have a db that is defined as "not logged". When my user executes a
particular job, he fills logical log files with the following entries.
The code he executes is from a third-party vendor and we cannot get a
look at the source, however, the UNIQID entry is for a serial being
assigned to a row.

My question is how can you have begin/commit entries for a non-logged
db?

addr     len  type     xid      id link
18       40   BEGIN    168      9737 0        12/02/1999 23:26:41
4102     gim2u
sr
40       36   UNIQID   168      0  18       80000c   1860673
64       36   COMMIT   168      0  40       12/02/1999 23:26:41
88       40   BEGIN    148      9737 0        12/02/1999 23:26:42
4094     gim2u
sr
b0       36   UNIQID   148      0  88       80000c   1860674
d4       36   COMMIT   148      0  b0       12/02/1999 23:26:42
1018     40   BEGIN    170      9737 0        12/02/1999 23:26:43
4108     gim2u
sr
1040     36   UNIQID   170      0  1018     80000c   1860675
1064     36   COMMIT   170      0  1040     12/02/1999 23:26:43
1088     40   BEGIN    182      9737 0        12/02/1999 23:26:43
4112     gim2u
sr
10b0     36   UNIQID   182      0  1088     80000c   1860676
10d4     36   COMMIT   182      0  10b0     12/02/1999 23:26:43
10f8     40   BEGIN    174      9737 0        12/02/1999 23:26:43
4107     gim2u
sr
1120     36   UNIQID   174      0  10f8     80000c   1860677
1144     36   COMMIT   174      0  1120     12/02/1999 23:26:43
1168     40   BEGIN    142      9737 0        12/02/1999 23:26:43
4099     gim2u
sr
1190     36   UNIQID   142      0  1168     80000c   1860678
11b4     36   COMMIT   142      0  1190     12/02/1999 23:26:43
.
.
.
.
.

Thanks....
Doug McAllister
Fidelity Invetsments

  doug.mcallister.vcf
< 1K Download
 
 
 

logical log entries for unlogged db

Post by Roland Baumschlage » Sun, 31 Dec 1899 09:00:00


not only update, insert or delete statements create entries in the
log-files. also create and drop table are making inserts into the log-file.
this category of entries could not be turned off, but the number of entries
normaly are reduced to a very small number of entries.

for example creating temp-tables permanetly in the database-area are often
used.

hope i could answer your question

roland baumschlager


Quote:>Hi all..

>I have a db that is defined as "not logged". When my user executes a
>particular job, he fills logical log files with the following entries.
>The code he executes is from a third-party vendor and we cannot get a
>look at the source, however, the UNIQID entry is for a serial being
>assigned to a row.

>My question is how can you have begin/commit entries for a non-logged
>db?

>addr     len  type     xid      id link
>18       40   BEGIN    168      9737 0        12/02/1999 23:26:41
>4102     gim2u
>sr
>40       36   UNIQID   168      0  18       80000c   1860673
>64       36   COMMIT   168      0  40       12/02/1999 23:26:41
>88       40   BEGIN    148      9737 0        12/02/1999 23:26:42
>4094     gim2u
>sr
>b0       36   UNIQID   148      0  88       80000c   1860674
>d4       36   COMMIT   148      0  b0       12/02/1999 23:26:42
>1018     40   BEGIN    170      9737 0        12/02/1999 23:26:43
>4108     gim2u
>sr
>1040     36   UNIQID   170      0  1018     80000c   1860675
>1064     36   COMMIT   170      0  1040     12/02/1999 23:26:43
>1088     40   BEGIN    182      9737 0        12/02/1999 23:26:43
>4112     gim2u
>sr
>10b0     36   UNIQID   182      0  1088     80000c   1860676
>10d4     36   COMMIT   182      0  10b0     12/02/1999 23:26:43
>10f8     40   BEGIN    174      9737 0        12/02/1999 23:26:43
>4107     gim2u
>sr
>1120     36   UNIQID   174      0  10f8     80000c   1860677
>1144     36   COMMIT   174      0  1120     12/02/1999 23:26:43
>1168     40   BEGIN    142      9737 0        12/02/1999 23:26:43
>4099     gim2u
>sr
>1190     36   UNIQID   142      0  1168     80000c   1860678
>11b4     36   COMMIT   142      0  1190     12/02/1999 23:26:43
>.
>.
>.
>.
>.

>Thanks....
>Doug McAllister
>Fidelity Invetsments


 
 
 

1. remote db restore continuous logical log recovery

I have a customer that wants to do the following:

1. they have a primary db on a box in atlanta
2. they have a secondary (drp) db on a box in washington
3. they want to take a level 0 ontape (could be onbar) of primary
4. send this level 0 to washington and restore secondary from level 0
5. Then from this point on they want to send the logical logs to
washington and continually keep the secondary db up to date with in 8
hours of the primary.

I have mentioned to them that they would be better off with Data
Replication. However, they are not comfortable with that. Do you know
if what they have proposed above will work?

If you can point me to some documentation, let me know and I will look
it up myself.

Thanks,
Gary

2. Why doesn't column name display?

3. [Fwd: remote db restore continuous logical log recovery]

4. replication between 2000 and 6.5 login fails . pls help. urgent!

5. logical restore - end log marked as end log ?

6. Defer checking a constraint

7. Freeing logical logs (log usage script)

8. SQL 6.5 Allocation Discrepany

9. Physical Log and Logical Log

10. Mass Delete - Log Entries Kills Available Log Space

11. Trx log backup - how suppress event log entries?

12. Entries in DB2DIAG.log and NT-Event-Log when connecting

13. Changing the logical name of data and log files