rvasanth

If this is more for documentational purposes, and not something you are trying to run live for every query, I think i have a potential solution. As already...

it's not truncating the data, jsut the display of it;

change this setting in SSMS: it's Under Tools>>Options; the default is to limit the results to 256 characters, like you've identified.

ok, still easy to do...can we assume the query results will be seen in text mode?

yes, if you have a valid username/password, you can connect multiple times.

different people can connect from other computers using the same username and password as well.

there is no practical limit...

i feel for you;

i did a search for "ascii art hearts" and found lots of examples;

i found this nice one ad wrapped it with the SELECT...UNION ALL, same that your...

I've got a snippet I put together that searches for invalid views/procs/functions; if those objects don't compile anymore, it has to be due to a dependent object like a table...

a fairly common question, actually; search for "unused procedures" and "unused tables", you'll see a ton of discussions, all pointing to Lutz's conclusion: any process, whether a trace or anything...

damn Lutz; your's looks much better than mine, so i decline to post it 🙂

very nice job.

blade, if you look at Lutz's contribution, it's doing all your updates as calculations...no...

table variables are notoriously slow when they get a lot of data in them, because they cannot take advantage of statistics; how many rows are in the table variable @LENNOXBILLING?...

here's the second part of your calcualtion as well, i think:

;with myCTE as (

select row_number() over (order by odometer,event) as comprow,* from

(

select row_number() OVER (PARTITION BY odometer,event order by...

clive thank you for making this so easy....the table definitions and data helps enourmously!

you rock!

here's how i'd "ignore" the double events in a row; i'm using row number and a...

sorry thought this was pure SQL;

i belive in SSIS, you have...

looks like you'll need to add a trace specifically for login events.

it's not part of the default trace, i both tested it and checked the default trace's definition...no login audits...

goodguy, why not build a view that creates the summary that you are looking for?

I avoid at all costs replacing detail data with summary data...besides the possbility of a mistake,...

three part naming conventions is how i often do it:

Select ColumnName from DBname1.dbo.Table

UNION ALL

Select ColumnName from DBname2.dbo.Table

UNION ALL

Select ColumnName from DBname3.dbo.Table