Jason, you forgot to mention:

"put the pork chops in the launcher and aim to a clueless OP or wannabe DBA":-D

OK, that's fine...

You just have to make a small additional effort and change the sample data you posted into something like:

INSERT INTO #Table

SELECT values UNION ALL SELECT values ... etc

And...

That's...

That record belongs to an uncommited transaction.

What I find strange is that after stopping /starting the service (which I would never have recommended!!!), all uncommited transactions should have gone rolled...

Fill the blanks and you'll get your answer:

--Drop temporary table

IF OBJECT_ID('tempdb..#tblStmtChar') IS NOT NULL DROP TABLE #tblStmtChar

--Create temp test table

CREATE TABLE #tblStmtChar(

CSNum smallint NOT NULL,

CharNum int NULL,

StmtNum int NOT NULL,

SurveyNum...

I'll quote myself as Steve did:

A few answers from these forums won't turn a wannabe DBA into a real DBA.

He had the job, so, why bother?

Now we may just hope...

Glad I could help.

Look up the ROUND function in BOL.

ROUND(number, 2) should do the job.

GabyYYZ (10/21/2009)

---

I've been wondering if people who accidentally stumble onto the first page of the THREAD and casually go from page to page, not realizing how long it has grown?...

It's very strange that you don't get distinct values, there must be something different within the two records you posted.

Try grouping by SystemUser, I think this is what you are...

I don't like that script, does too many things behind the scenes.

Why not simply:

SELECT TOP 1 1 FROM remoteserver.dbname.dbo.sometable

or, even better if the remote server is SQL Server

SELECT TOP 1...

A few answers from these forums won't turn a wannabe DBA into a real DBA.

He had the job, so, why bother?

Now we may just hope he will study hard and...

Try this:

SELECT DISTINCT CONVERT(datetime, CONVERT(char(8),LoginTime,112), 112) AS [date], [Applicationtype], [SystemUser]

FROM DW.ServerLogonHistory

ORDER BY CONVERT(datetime, CONVERT(char(8),LoginTime,112), 112)

Yep.

Very easy to try, indeed.

Great idea, Gail.

I never have thought about that!

The main point, however, is that the piece of code (stored procedure, application code etc...) that requested the transaction to start is responsible...