Any way to find user who did update in SQL SERVER?

Hi there,

Is there any way to find the person or user who did update transaction
manually
in query analyser and not through application in certain time?
As i have check thru log file but cannot find anything.

Any command or software to check it?

Thanks for the help!On Nov 20, 6:45 pm, LaMoRt <cwe...@.gmail.comwrote:

Quote:

Originally Posted by

Hi there,
>
Is there any way to find the person or user who did update transaction
manually
in query analyser and not through application in certain time?
As i have check thru log file but cannot find anything.
>
Any command or software to check it?
>
Thanks for the help!

Try running

sp_who
sp_who2
Profiler|||On Nov 20, 6:45 pm, LaMoRt <cwe...@.gmail.comwrote:

Quote:

Originally Posted by

Hi there,
>
Is there any way to find the person or user who did update transaction
manually
in query analyser and not through application in certain time?
As i have check thru log file but cannot find anything.
>
Any command or software to check it?
>
Thanks for the help!

Duplicate of http://groups.google.com/group/comp...28b3b6e9b5b1558

Any way to bold certain words in data field?

I'm working on cleaning up a report and got a request to bold certain words within a data field. I have no idea where to start or what to search on to do this. For instance, I would want to bold any occurance of "History:" or "Technique:" but not bold "history". The data is coming over as plain text in one large data field. Any help would be greatly appreciated!

Thanks!We used to have a system that fed us the data in seperate fields of
History:
Technique:
Comparison:
Findings:
Conculsion:

but now we have a system that is unable to split the data elements up before feeding it into our system. We can't add any formating on the upstream system either unfortionately. Now our report looks like garbage lol. Hopefully one of you gurus will be able to help.

Any special care for CLR code when moving to other servers

I am pretty certain that once you create an assembly referring to a dll on
one server, and i decide to move that database to another server, the
assembly goes with it as part of the database and I dont have to recreate
the assembly or move the dll to the other server.. am i right ?Yes, you are right, the assembly is part of the database, even if you move
the database to another database server.
Also notice that by default on SQL Server CLR Integration is disabled so you
may need to enable it first.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> I am pretty certain that once you create an assembly referring to a dll on
> one server, and i decide to move that database to another server, the
> assembly goes with it as part of the database and I dont have to recreate
> the assembly or move the dll to the other server.. am i right ?
>
>

Any special care for CLR code when moving to other servers

I am pretty certain that once you create an assembly referring to a dll on
one server, and i decide to move that database to another server, the
assembly goes with it as part of the database and I dont have to recreate
the assembly or move the dll to the other server.. am i right ?Yes, you are right, the assembly is part of the database, even if you move
the database to another database server.
Also notice that by default on SQL Server CLR Integration is disabled so you
may need to enable it first.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:
> I am pretty certain that once you create an assembly referring to a dll on
> one server, and i decide to move that database to another server, the
> assembly goes with it as part of the database and I dont have to recreate
> the assembly or move the dll to the other server.. am i right ?
>
>

Any special care for CLR code when moving to other servers

I am pretty certain that once you create an assembly referring to a dll on
one server, and i decide to move that database to another server, the
assembly goes with it as part of the database and I dont have to recreate
the assembly or move the dll to the other server.. am i right ?
Yes, you are right, the assembly is part of the database, even if you move
the database to another database server.
Also notice that by default on SQL Server CLR Integration is disabled so you
may need to enable it first.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Hassan" wrote:

> I am pretty certain that once you create an assembly referring to a dll on
> one server, and i decide to move that database to another server, the
> assembly goes with it as part of the database and I dont have to recreate
> the assembly or move the dll to the other server.. am i right ?
>
>