No thats just a LSN number, that would be the marker in the transaction log where the transaction started

No, when you run a shrink with Truncate Only you reset the LSN's.

If you just run DBCC SHRINKFILE you dont reset the LSN's

Dont kill the UOW, first find the host which initiated the DTC transaction and see if it is still active on that host, if it is terminate it, if not...

L' Eomot Inversé (7/26/2012)

---

Came across something different the other day: Crabbies spiced orange alcoholic ginger beer. I think I prefer it to their ordinary alcoholic ginger beer, at least...

No it wont use UDP 1434, thats the browser port.

The whole part of the browser is that it diverts the traffic to the correct ports, so you dont need to...

Now this just gets stranger every post.

Can you provide the CREATE TABLE script for the table in question?

So the output of the below returns 0 | 1

SELECT ISDATE('2012-07-29 00:05:28.819'), ISDATE('2012-07-29 00:05:28')

Only use REPAIR.... options as a last resort, drop and recreate of the index would be the prefered option IMHO.

Important note

Use the REPAIR options...

You have all the information you need in DBCC OPENTRAN, it gives you the SPID, so all you need to do now is query the DMV's to find out what...

didi77 (8/6/2012)

---

anthony.green (8/6/2012)

---

Shrink the file, but dont use truncate only.

You will need to ensure that the reuse desc is set to nothing to shrink it down as low as possible,...

you can run the procedure

sp_cycle_agent_errorlog

At a certain point to create a new log file.

We do this once a month to both the SQL and Agent logs.

Shrink the file, but dont use truncate only.

You will need to ensure that the reuse desc is set to nothing to shrink it down as low as possible, otherwise it...

Lavanyasri (8/6/2012)

---

when i try to run the dbcc opentran() on that particular database its showing the below open transaction

Transaction information for database

Oldest active transaction:

...

franck.maton (8/6/2012)

---

@anthony-2.Green

I could, but I've more than 3.600.000 records for today. But it's like:

2012-08-06 00:05:28.819

2012-08-06 00:05:28.819

2012-08-06 00:05:28.819

2012-08-06 00:05:28.819

2012-08-06 00:05:28.819

2012-08-06 00:05:28.819

2012-08-06 00:05:28.819

2012-08-06 00:05:28.820

What are you thinking of ?

@Cadavre

Yep, i'm working on...

Can you provide the CounterDateTime values

SELECT CounterDateTime

FROM [MSSQL_PerfmonCollector].[dbo].[CounterData]

WHERE CounterDateTime LIKE '2012-08-06%'

Assuming you use ISO formatting, other wise change the like to match...