Last night I hosted a session about the Visual Studio 2010. Speaker was Gerard van der Pol from Microsoft NL. This time it wasn’t about what’s new with the (obviously) improved IDE and .NET Framework 4, but it was all about the features regarding Team Foundation Server (TFS). Of course, there are lot of new features to talk about and so little time. I’ll describe some features Gerard was demonstrating.

First, let me say that the title of this post is a bit wrong. The brand Team System will disappear, so it is only Visual Studio 2010.

Also, the editions will change a bit:

Regarding to Team System (or should I say ALM) there are 2 new products: Visual Studio Test Elements and Visual Studio Team Lab Management.

With Lab Management it is possible to create and configure your environments to help testers more easily test a variety of configurations in a virtual lab environment, and help developers more easily repro bugs by delivering snapshots of those virtualized environments after bugs are discovered. For more information, watch this Channel9 video.

With Test Record & Playback you can actually record and playback your test plan and steps. The video’s will be accessible for the developer from the work item. For more information, watch this Channel9 video.

Do you recognize this:

• You’ve received reports of a crash from a tester, but on your local box you can’t get the bug to reproduce.
• You’ve received a crash dump from the tester along with the bug. But the call stack that actually caused the crash was just a cascading effect and you can’t trace the bug back to the root issue.
• The bug that you are currently working at resolving has an extremely long set of reproduction steps and you just accidentally stepped over the function that is returning bad data.

IntelliTrace, formerly known as Historical Debugging, can help you out now! IntelliTrace is similar to that of a black box in a plane. It’s keeping track of important points in your programs execution and allow you to play back what happened at those points at a later time. For more information, click here.

With the new Profiler you get a really great look at how your code is performing. It comes with couple of new features for developers:

• CPU Sampling
  Measures CPU-bound applications with low overhead.
• Instrumentation
  Measures function call counts and timing.
• .NET Memory Allocation (Sampling)
  Track managed memory allocation.
• Concurrency
  Detect threads memory for other threads.
  • Collect resource contention data
  • Collect thread execution data

Profiler includes a new page called the Function Details page, which will depict the caller/callee information in a graphical way along with the performance metric. You can also view your code which includes the line-level performance measurements.

To end this post, I want to tell you about Gated Check-in. We all have colleagues who are checking in their code and you end up with a non building solution. With Gated Check-in you can prevent users to check-in their code unless it all builds! And it is also possible to run your tests too, before allowing to check-in.

For more information, click here.

I was truly amazed with all the new features of Visual Studio 2010 regarding ALM and had a great night. Go explore for yourself!

The Profiler opens in July, 1974 on Miss Black’s first day on the job at NYPD. As retiring cop Deckard is showing her the ropes, neither of them suspect the events that are about to unfold. As they’re investigating seemingly random crime scenes, patterns begin to emerge. Is this the work of one person?
Now the hunt is on, and it’s up to you to search for clues and piece the evidence together and create a profile of the perpetrator. Can you stop a killer before he strikes again?

Profiler full game features:

• Hunt for clues to reveal the identity of a serial killer
• Create a profile of the perpetrator

http://www.takeongames.com/pcgame/profiler/2169

Warum einfach, wenn es auch kompliziert geht: die Verkabelung eines Netzwerkes zu dokumentieren ist eine interessante Aufgabe. Stößt man doch auf Kabel, die nirgendwo hin führen, die nicht dorthin führen wie es geschrieben steht oder dazu dienen, Musik statt Daten zu transportieren. Es ist fast so spannend, wie einen Weg aus einem Labyrinth zu finden.

Im Nachhinein ist alles ziemlich simpel – eben nur scheinbar kompliziert umgeben von strahlender Aura der Intelligenz. Spuren ins Dunkel, kryptische Bezeichnungen, falsche Fährten und Überraschungen: Das berühmte: “Ja dann!” oder “Oder so!”. Natürlich unbewusst, nicht gewollt, unterstelle ich positiv.

Jeder hinterlässt durch sein Tun Spuren. Nicht seine Notizen oder Unterschriften meine ich. Nicht das, was man anfassen kann, sondern: Sein Profil, sein Denken, sein Verhalten, welches sich in Erscheinungen abbildet und einen Schluss zulassen: das war so ein Typ, es konnte kein anderer sein, es ging nicht anders. Ein anderer hätte andere Spuren hinterlassen.

Ich glaube, dass nennt man Profiling. Fälschlicherweise. Liest du hier bei Wikipedia.

Olá!!! Ando cheio de assunto, mas meio sem tempo pra escrever. Entretanto resolvi dar uma pausa pra dar uma dica sobre um recurso importante de banco de dados que estava utilizando neste momento. Estou falando do “Profiling”, isto é, a capacidade de bisbilhotar o que está acontecendo por detrás dos panos, seja na execução de um programa, ou nesse caso, de um banco de dados.

O SQL Server da Microsoft possui uma ferramenta, o Profiler, que realiza muito bem essa tarefa, permitindo ao desenvolvedor monitorar o que ocorre no banco enquanto o mesmo está em uso. Eu utilizo este recurso principalmente para verificar os erros que cometo nas consultas que não resultam em exceções, isto é, erros lógicos.

Entretanto como tenho clientes que utilizam o MySql, sentia muita falta de uma ferramenta similar. Após muito pesquisar, encontrei uma forma simples de obter o mesmo resultado sem o uso de nenhuma ferramenta específica. Basta habilitar o log do MySql. É isso, simples assim. Para isso, no meu caso (MySql no Windows), basta editar o arquivo “C:\Arquivos de programas\MySQL\MySQL Server 5.0\my.ini” e inserir a linha:

log=”C:/Arquivos de programas/MySQL/MySQL Server 5.0/Data/sqllog.log”

Eu inseri essa linha logo abaixo da linha:

port=3306

O nome e o caminho do arquivo podem variar, é claro. Feito isso, basta reiniciar o serviço do MySql para que todas as consultas realizadas sejam armazenadas nesse arquivo.

Vale a pena lembrar que em um servidor de produção esse arquivo poderá crescer rapidamente, então não se esqueça de desabilitar essa opção caso não haja mais a necessidade do profiling. Para isso basta inserir o caractere # no início da linha que foi adicionada.

É isso aí, em breve espero estar de volta com um assunto muito mais interessante relacionado à performance de sistemas.

Dean Graziosi’s name has always been synonyms with the words real estate millionaire. He is currently based in Phoenix, Arizona and has been writing a lot of selling books, videos and audio courses about financial planning and investment.

Having no formal education in finance, Dean learned real estate investment by himself. He has reach that real estate success with only a high school diploma and real-life world experience. Having that real estate motivation, keen observation and experience brought him to where he is now.

His book “Be A Real Estate Millionaire: Secret Strategies for Lifetime Wealth Today” is exemplary how to put Dean’s system into action. All the wealth secrets he have learned over the last two decades have been compiled in this bestselling book. Going a step further than most investment experts, Dean makes himself available to readers through his seminars, where those interested can learn more of his investment strategies and commercial realestate mindset.

So why is Dean so famed in real estate investment? Is it because of his real estate success that people started looking up to him? No. It is because he was able to reach out to people around the world with his books, sharing his wealth secrets in real estate investments. He has successfully passed on to people techniques that will really inspire aspiring investors.

The connections between people are what drive the market – and Dean understands this. The real estate market is more than buildings, lots and numbers; there are people behind these transactions. By knowing how people think and relate to one another, a leg up can be gained in the investment field. Dean has a unique perspective on how real estate investing works, and is a born educator who can get his ideas across to others effectively.

Dean Graziosi  is a man who knows from personal experience that someone, anyone who wants to succeed in real estate investments can. For nearly ten years, he has been helping others achieve the success that he himself has been able to. Anyone who is willing to learn the ins and outs of real estate investment has a good friend in Mr. Graziosi.

I know what you’re thinking, and the answer is YES. It does remember all of the settings each time you open it! You’ll be able to save and load configurations shortly, too.

The Jigsaw Man I’ve just finished reading this book and oh boy can Paul Britton put pieces together. It’s no wonder his book is called The Jigsaw Man! This chap, who hails from the Midlands, is a psychologist and offender profiler who over the years has given – free of charge, I might add – a fair chunk of his time to help police solve crime.

When I pulled open the first page of the book I was expecting it to be about an American, for some reason. Aren’t all decent crime stories from the US? Well, no actually. I found myself visualising Paul Britton at work in Leicester, the city where I lived for a couple of years, and visiting places I know relatively well. He started from humbled beginnings but worked his arse off to become a very talented psychologist, helping police track killers and kidnappers, offering interview techniques and piecing together the pieces of some horrific crime scenes.

Britton’s path crosses some horrible events – Fred and Rosemary West’s appalling killing spree in Gloucester; the distressing murder of toddler Jamie Bulger by two 10-year-old boys; the violent and sexual murder of a young woman and her small child; the brutal slaying of Rachel Nickell on Wimbledon Common and the abduction of baby Abbie Humphries; and he meets the man who killed his own wife and made up an elaborate tale of kidnap and gangs to cover it up.

In his autobiography, forensic psychologist Paul Britton asks himself four questions when faced with a crime: what has happened; who is the victim; how was it done; and why? Only when he has the answers to these questions can he address the fifth: who is responsible? While the book is a tad slow to start for my liking – but only because I like the blood and the gore – I soon found myself glued to the pages and the interesting police cases he was consulted on.

While clearly a very talented man in his field, an area which isn’t supported by everyone, Britton admits that with each case he left a little piece of himself at the scene. So why did he do it when he found it so harrowing? Why pore over crime scene photos into the early hours while his family slept? Because he knew if he could help put one more evil person behind bars, the streets would be a safer place. And that’s what drove him. Each time he promised to hang up his offender profile hat, a new and intriguing case would come along and he just couldn’t say no.

What’s also interesting is how he can’t meet people now without finding out all sorts of information about them that he’d rather not know. The way people dress, act, speak and carry themselves all give off not so subtle signals about the sort of person they are or how easy a victim they’d would make – and Paul Britton finds it tricky to ignore these signals even during a casual conversation.

While his profiling has clearly eaten away at him over the years, he has assisted the police in more than 100 cases, helping them to identify and understand the nature of the perpetrator. It’s a good book and not only a detective story, but an insight into what makes the criminal mind tick. It sure gets a thumbs up from me, and if you enjoy real crime stories then this is for you.

I had to sit down and figure out exactly what to do about SlimTune. People really, really like that little thing, which is amazing for something I put together in six weeks. It doesn’t deserve to die, so I’m going to make sure it doesn’t. That said, it looks like it will be a while before I get back to it. January, to be exact. Unfortunately, I need to buckle down and finish my degree right now, and I can’t really afford to commit to a side project.

That’s the bad news. The good news is that I haven’t stopped thinking about the project, and I’ve figured out how to do some really sweet stuff. Let’s recap. The current release of SlimTune is a purely sampling based profiler. The goal is to enable instrumentation and hybrid modes for public use. They actually already work, except the data is thrown away by the frontend. I’ve been unsure of how to collect it in a useful way, but I’ve got some ideas now that will give you some serious detail. Min/average/max will be there, but who cares? I can give you a graph with timings, showing you the actual characteristics of the function. So if it often takes 5ms or 50ms, but nowhere in between, you’ll see two spikes at 5 and 50. The average might be 30ms, but that’s basically a bogus number in these situations.

I’ve also got some UI improvements scheduled. Probably chief among them is to fully enable custom visualizer plugins, so you can throw together your own views of the data. I’d really like to enable some kind of graphing support, but we’ll have to see how that goes. It’s tricky to find a chart control that also has favorable distribution terms. I was using MS’ chart control for the teaser photos, but it really sucks — or at the very least, I don’t understand how to use it the way I want to. Things get sized very strangely, for example. I’ll figure something out.

Oh, and people are practically begging for a way to save and load launch configurations. I promise you, that’s top of the list. It annoys me too. I did it in six weeks, remember? It will be fixed.

Now, here is the important bit. For those of you who are interested in SlimTune, I have a request! File issues against the profiler for anything you want. And I don’t just mean bugs. UI and other feature requests are welcome! You can even request things I’ve promised I will do. That’s totally fine. Hit me with everything you’ve got people! That way I know what’s most important to YOU, not me.

Mittlerweile kann ich eine DVD-Sammlung von über 350 DVDs mein Eigen nennen.

Damit ich nicht den Überblick verliere nutze ich das Programm:

DVD-Profiler

Es ist keine Freeware, sondern kostet z.Z. 29,95 USD. Der Preis war es mir aber vor Jahren wert, denn bislang ist mir kein besseres Programm unter die Augen gekommen.

Man kann die Software zwar auch kostenlos nutzen, allerdings darf dann die DVD-Sammlung nicht mehr als 50 DVDs beinhalten.

Das Einspielen neuer DVDs funktioniert allein durch das eingeben der UPC Nummer (Strichcodes) von der Rückseite der DVD-Hülle. Alle DVD spezifischen Informationen (Titel, Cover, Darsteller, etc.) werden dann via Internet eingelesen. Einfacher geht es nicht mehr…

Die eigene DVD-Sammlung kann man auf seinem Rechner verwalten und/oder sie ins Internet stellen.

Hier geht es zu meiner online DVD-Sammlung: Nimbert

Gibt es da draußen noch jemanden der dieses Programm nutzt?

Running the Profiler GUI against a production server is not something you should do. I’ve outlined my research into exactly why in the past. But I hit another little issue with the Profiler GUI as part of work I’m doing on a Microsoft PSS call (more on that in another post). We have a procedure on one of our systems that is erroring out, but only on a particular server and only when called from the application, not when it’s called, on the same server, from SQL Server Management Studio.

I needed to capture some trace events and do it quickly, so I decided to use the GUI, just this once. I put filters on it so that I would only collect certain data, and the database I was collecting from was not in active use, so I knew the only commands I’d be capturing were my own. I just captured SQL:BatchCompleted and SQL:BatchStarting. I needed to run the query one time to validate the behavior. Under these circumstances, with full knowledge of what the GUI can do to a production system, I figured I was ok.

I kicked off the trace through the GUI and ran my proc. Here’s what I saw:

This is not evidence of the problems outlined above. You know how TextData normally shows the query that is being run? In this case the query being run involves a rather large XML parameter being passed in as part of the query. This is so large that the Profiler GUI skipped over it and didn’t bother clogging  the memory of the system or my network with capturing it. Don’t panic though. If I run the exact same trace as a server side trace, I get the full text of the call in the TextData field. And yes, if you’re wondering, I’m pretty positive this is by design (although the only reference I can see in BOL is to events greater than 1gb, which we are not into here).

On more reason to avoid the Profiler GUI as a data collection mechanism.

Reports summaries of connections, running requests, open transactions, open cursors, and blocking at 3 different levels of aggregation detail.

Also gives the piggiest running request for each grouping along with its identifying information, query batch text, statement text, and XML query plan.

Most useful for finding SPIDs thare being hoggy right now – activity monitor gives session-scoped resource consumption, this aggregates active request scoped resource consumption.

Also useful for quickly finding blocking offenders and finding programs that are not closing connections, cursors or transactions.
Returns 3 result sets:

The Ultimate Connection Summarizer and Trouble Finder – SQLServerCentral.

“Zero’nun tadı Coca-Cola ile aynı olabiliyorsa, sizinle aynı birisi de olabilir!” sloganıyla Coke Zero “facial profiler” uygulaması kullanarak Facebook üzerinden size benzeyen, dijital ikizinizi buluyor. Eğer Facebook hesabınız varsa durmayın, bağlanın ve kendinizle tanışın. Neden olmasın?

If ever you notice that your queries are running slow and think that memory is the culprit, do run this query. If there are lots of rows in the result, please try to optimize the queries or increase the memory capacity.

SELECT TEXT, query_plan, requested_memory_kb,
granted_memory_kb,used_memory_kb, wait_order
FROM sys.dm_exec_query_memory_grants MG
CROSS APPLY sys.dm_exec_sql_text(sql_handle)
CROSS APPLY sys.dm_exec_query_plan(MG.plan_handle)

via SQL SERVER – Queries Waiting for Memory Allocation to Execute « Journey to SQL Authority with Pinal Dave.

Lesetips: I siste utgave av det svenske magasinet Axess har Pär Sandin en artikkel om hvordan den greske dramatradisjonens far – Homer (som muligens var mer enn én person) – skapte den invidualiserte helteskikkelsen (uthevelsene i fet skrift er mine):

De homeriska eposen har också ett innehåll som skiljer dem från den grekiska mytologiska berättartraditionen i allmänhet. De mest iögonfallande detaljerna, spänning och äventyr, ”action” och krigsskildring som i Iliaden, ”fantasy” som i Odysséen, gudar, monster och övernaturliga väsen, allt det förekommer i riklig mängd i alla grekiska sagor. Det som istället skiljer Homeros från mängden och gör honom till den främste var människoskildringen. Det var vad man ville höra: Hur var dessa människor, dessa hjältar som levde före oss, beskaffade? Vad var det för individer?

Intresset för det individuella och det mänskliga är en nyckel till själva den forngrekiska kulturen. Sokrates spekulerar i sitt försvarstal inför atenarna, som ville avrätta honom för gudlöshet, om ett paradisiskt liv efter döden (som ett gott alternativ till ett annat gott: den eviga, drömlösa sömnen). Är det då ro och njutning som hägrar? Nej, det är att få träffa de härliga döda! Att få skaka Homeros hand, det var paradiset för Sokrates: de andra är paradiset. Så när det ibland påstås att individen är något som uppfanns i Västeuropa på 1800-talet, är det felaktigt: individen uppfanns av Homeros. Odysseus och Akilles är de mest individuella av alla individer, och Helena, Ajas, Hektor, Paris, Agamemnon och Nestor är inte typer som man senare i Aristoteles klassicistiska tradition ville litteraturteoretisera bort korten, utan individer.

“Med Homeros blev hjälten individ”

There’s a very common belief among DBA’s: Stored procedures are pre-compiled. I had someone tell me all about it just last week. There are lots of sources that say what I’m getting ready to say, so this really shouldn’t come as news to anyone,but it will. No, they’re not. Stored procedures are not pre-compiled.

When you create or update a stored procedure on the server, it gets a syntax check. But there is no compile process, let alone a pre-compile process. That stored procedure exists exactly as it is named, a procedure that is stored on the server. It’s just a collection of TSQL code, possibly with some parameters, waiting to be called. Until it’s called, it is not ready to be executed. Don’t believe me? I’m not a huge sports fan (except for MMA), but I’m willing to use a common sports expression. Let’s go to the slow motion instant replay, also known as trace events.

I’m going to run each one of the following statements, one at a time and capture a set of trace events, also listed below. First the code:

CREATE PROCEDURE dbo.MyTest
AS
SELECT *
FROM sys.dm_exec_query_stats AS deqs ;
GO
EXEC dbo.MyTest ;
GO
EXEC dbo.MyTest ;
GO
DROP PROCEDURE dbo.MyTest ;
GO

The events I’m capture are:

• SQL:BatchCompleted
• SP:CacheMiss
• SP:CacheHit
• SP:CacheInsert
• SP:CacheRemove

After I run the script, here is what is visible in the trace:

With the first statement to create the procedure, you see that there was a CacheMiss event, since the DDL statement isn’t cached. You’ll get a miss event every time this runs. Next, the execute statement runs and you can see another CacheMiss event followed immediately by a CacheInsert event. This is the creation of the execution plan and it’s addition to the cache. The statement completes and the second execute statement fires. This gets a CacheHit event, since the last execute created a plan, and then it completes. The final statement, again, DDL, so you see a CacheMiss event and then the CacheRemove event as the procedure is dropped.

Nothing was added to the cache until the procedure was called. There was no pre-compile process. None. To quote a popular television show, myth busted.

Til tross for 300 millioner medlemmer er ikke Facebook verdens største sosiale nettverk. Personlig mener jeg at nettbaserte sosiale nettverk har tre helt spesielle egenskaper: 1) Profiler som gjør at medlemmene kan vise sin identitet, 2) Mulighet for andre til å kontakte disse profilene, og 3) Det er enklere å lykkes for en gruppe mennesker som utveksler ideer og tanker enn for enkeltmennesker som ikke gjør det.

I forrige uke kunngjorde Facebook at de passerte 300 millioner brukere, langt flere enn på MySpace, for ikke å snakke om Twitter. Allikevel tør jeg påstå at Facebook ikke er størst. Den æren må vi tillegge e-post. Nye tall fra Microsoft viser nemlig at antall aktive brukere (selv om definisjonen på ’aktiv’ ikke blir forklart) overstiger 375 millioner brukere av Hotmail.

Hvis du kombinerer alle e-post nettverk fra Gmail, Hotmail, AOL, Yahoo og flere millioner Outlook-brukere i bedrifter over hele verden, blir dominansen over Facebook betydelig.

Ikke alle er enige i at e-post og sosiale nettverk kan sammenlignes
Jeg har diskutert dette med mange, og tar gjerne også opp diskusjonen her. For selv om de fleste er enige, er det noen som analytisk påstår at e-post ikke er et sosialt nettverk fordi 1) Det er privat, ikke offentlig, 2) Mangler profiler, og 3) Folk kan ikke finnes på samme måte. Jeg skal derfor være snar til å forklare hvorfor jeg mener at e-post er verdens største sosiale nettverk.

Sosiale nettverk kan være private
På samme måte som i det virkelige liv er det enkelte samfunn som ikke er åpne for alle. Faktum er at Facebook er et lukket sosialt nettverk hvor svært lite av din personlige informasjon ligger åpent for alle. For det andre er noen av de beste sosiale nettverk å finne i lukkede bedriftsmiljøer. Jeg tenker blant annet på Telligent, Mzinga, Awareness og Jive.

E-post har faktisk profiler
Mange sier at e-post ikke har profiler, mens e-post myntet på forbrukere alltid har profiler. Se bare på Yahoo, Microsoft Live og Google.

Der oppfordres vi til å registrere vår tittel, vårt navn, lokasjon og annen demografisk informasjon. Du kan også lese mye i signaturen i en e-post, hvor folk skriver sitt navn, bedrift, kontaktinformasjon og gjør sin profilinformasjon tilgjengelig for dem de ønsker å dele den med.

E-postprofiler kan finnes, og de er sosiale
De som måtte mene at e-post ikke er et sosialt nettverk påstår at profilene er vanskelige å finne. Et sosialt nettverk hjelper likesinnede brukere til å finne hverandre, og enkelte sosiale nettverk anbefaler i tillegg andre å bli med.

Se bare på bedrifter som benytter seg av utvekslingsservere med en lang liste med individuelle navn, profiler og grupper som de tilhører. Du kan søke etter titler, lokasjoner og grupper for å finne hvem i bedriften som har samme behov som du. Hva med nettbaserte forbrukernettverk? Yahoo oppfordrer sine e-postbrukere til å stille og besvare spørsmål fra hverandre – selv om du ikke kjenner folk personlig.

Enig eller uenig, e-post og sosiale nettverk overlapper hverandre
Ytterligere noen indikatorer på at e-post og sosiale nettverk er i ferd med å smelte sammen: For offentlige sosiale nettverk som Facebook, Glassdoor, Yelp og Twitter er e-post en nødvendighet for å kunne registrere seg. Meldinger du mottar i Facebook eller Twitter havner ofte i inngående e-post. Har du sett Yahoos hjemmeside i det siste? (Se illustrasjon) Den begynner å ligne på et sosialt nettverk!

“Love is not about finding the right person, but creating a right relationship. It’s not about how much love you have in the beginning but how much love you build till the end.” It’s true until now I love you deeply. I have this girl who really makes my world upside down. She’s been my inspiration ever since I was working, she has these extreme personality that freezed me. she is so “maldita” but “loving”, she is so “ma-arte” but “caring” and lastly she is a “shopping addict” but “thoughtful”, and more, with this extreme drivers around her, I still love her super with full volume. I have loved her more than anything in my life, thats for sure!… It’s just an extreme feeling, She is a kind of girl that I dream to have a family, have children and grow old with it.

Les tueurs en série diffèrent dans leurs mobiles et leurs attentes.
Simplifions à l’extrême :
la plupart tuent pour le pouvoir et le contrôle,
certains pour le sexe
et d’autres – surtout les femmes – pour l’argent.
D’autres, enfin, tuent parce qu’ils sont psychotiques et croient, par exemple, entendre des voix leur ordonnant de tuer.

Les différentes raisons pour lesquelles ils tuent

Ted Bundy tuait pour le contrôle.
Jerry Brudos tuait pour le sexe.
Joseph Kallinger tuait parce qu’une vision lui avait commandé d’éliminer tous les êtres de ce monde.
Richard Kuklinski tuait pour l’argent.
Beoria Simmons tuait des femmes qu’il pensait être de “sales prostituées”.

Les tueurs en série, même s’ils présentent de nombreux points communs, ne se ressemblent pas. Ils diffèrent non seulement dans leurs mobiles, mais aussi dans leur “gain anticipé” : en d’autres termes, le type de satisfaction qu’ils obtiennent en tuant. Ce sont ces distinctions qui les séparent dans des catégories distinctes (si l’on peut dire), que nous pouvons considérer, tant intellectuellement que légalement.

Il existe différents “types” de tueurs en série. Chaque type est distinct, unique. Toutefois, un serial killer convient rarement parfaitement à une seule catégorie sans se mélanger avec les autres.

La distinction initiale qui doit être faite concernant les tueurs en série concerne leur mobilité géographique. Certains vivent, travaillent et tuent dans une seule région, voire une seule ville.

John  Wayne Gacy est l’exemple parfais d’un serial killer géographiquement stable. Il prenait soin de tous ses besoins dans la région de Chicago : vivre, travailler et tuer.
Ted Bundy, au contraire, était un serial killer géographiquement mobile. Il a tué dans au moins neuf états. Il ne déménageait pas tant pour trouver des victimes que pour embrouiller la/les police(s).

Les types de serial killers

Selon la description du FBI, un tueur en série tue au moins trois personnes en plus de 30 jours, avec une période importante de calme, de non-action entre les meurtres.
Dans son livre, “Serial Murder”, Ronald Holmes développe une typologie des tueurs en série : celui qui a des visions, celui qui pense avoir une mission, celui qui tue pour le plaisir, et celui qui tue pour le pouvoir / contrôle.
Chaque type est classé selon le mobile et le “gain anticipé” du tueur. Certains mobiles sont sexuels, d’autres ne le sont pas.

Voici un bref aperçu des quatre “types” de serial killers défini par Holmes.

Le serial killer qui a des visions :

Joseph Kallinger a commencé à tuer près de chez lui. Il a tué l’enfant d’un voisin, puis une jeune femme, et enfin son propre fils. Son plan était de tuer absolument tout le monde sur la planète, et ensuite, de se suicider.
Pourquoi ? Il expliqua que “Charlie,” une tête désincarnée, flottait dans sa chambre et lui ordonnait de tuer. Même après plusieurs années d’hospitalisation, Kallinger soutenait encore que Charlie lui rendait toujours visite.
Psychotique, souffrant d’une rupture totale avec la réalité, ce type de serial killer reçoit des ordres provenant de voix ou de visions, qui lui demandent de tuer.
(J’en profite pour ouvrir une parenthèse et rappeler encore une fois que la majorité des personnes ayant des problèmes mentaux n’est pas violente et que la plupart des tueurs en série sont sains d’esprit !)

Le serial killer qui pense avoir une mission :

Ce tueur veut débarrasser la communauté d’un “élément indésirable”. Qui sont les “indésirables” ? Cela dépend uniquement de l’opinion du tueur.
Ils/elles peuvent être des prostitué(e)s, des drogués, des homosexuels, ou qui que ce soit ayant une race, un sexe, une profession ou une caractéristique (réelle ou imaginaire) que le tueur estime “indigne”.
Ce tueur n’est pas psychotique. Simplement, il décide de “rendre personnellement un service” au monde, à la communauté ou à son voisinage : l’éradication d’un groupe de personnes spécifiques qui sont les “éléments indésirables” de SON monde.
Dans le monde de Beoria Simmons, les “indésirables” étaient les prostituées. Dans celui de Ted Kazinsky c’était la technologie moderne et ces représentants, les scientifiques.

Pour ces deux types de tueurs, le sexe n’est PAS un facteur de motivation.

Le serial killer qui tue pour le plaisir :

Il y a trois “sous-types” dans cette catégorie :

• celui qui tue par avidité sexuelle
• celui qui tue “pour le frisson”
• celui qui tue pour son confort
  Les deux premiers, alimentés par leurs fantasmes, tuent pour ressentir un plaisir de nature sexuelle.

Le premier, le “lust killer”, est un prédateur sexuel attiré autant par les victimes vivantes que par les cadavres.
Jerome Brudos a commencé par un fétichisme des pieds, puis est passé au meurtre, à la mutilation sexuelle et à la nécrophilie.

Celui qui tue “pour le frisson”, le “thrill killer”, exige une victime vivante afin de “se nourrir” de la terreur de celle-ci. Le meurtre est un processus lent et déchirant, qui donne au tueur plus de temps pour jouir de la souffrance de sa victime.
Il voit ses meurtres et l’enquête de la police comme un jeu. Il adore l’attention que lui portent les médias et la police, et le fait qu’il est capable d’échapper aux autorités. Il a tendance à garder une sorte de “registre” de ses meurtres, par exemple des coupures de presse qui décrivent ses crimes. Il s’amuse à déjouer les efforts de la police.
Les “Hillside Stranglers” (les cousins Kenneth Bianchi et Angelo Buono) étaient des “thrill killers” qui torturaient leurs victimes.

Le troisième “sous-type”, celui qui tue pour le confort (le “comfort killer”) tue pour des raisons très “terre-à-terre” : l’argent, les bénéfices d’assurance ou de business.
Kuklinski, un tueur professionnel qui a admis avoir tué plus de 100 personnes, entre dans cette catégorie. Il n’y a pas d’aspect sexuel dans ce type de meurtre ; le “but anticipé” est d’obtenir de l’argent et de vivre “la belle vie”.

Les championnes des “comfort killers” sont les “veuves noires”, qui tuent leurs maris et amants pour hériter ou toucher l’assurance-vie.
Le “bon” Docteur Shipman a assassiné ses patientes après les avoir poussées à modifier leur testament en sa faveur.
Bien que beaucoup de gens puissent ne pas considérer les assassins ou certaines personnes payées pour tuer comme des tueurs en série, je pense qu’il ne devrait pas y avoir de distinction simplement parce que le “gain anticipé” est un profit matériel plutôt que psychologique ou sexuel.

Le serial killer qui tue pour le pouvoir, le contrôle :

La motivation de ce type de tueur est centrée sur le besoin de pouvoir et de domination. Comme Bundy l’a fait remarquer une fois, posséder la vie d’une personne comme “une plante en pot ou une Porsche,” est une sensation incroyable. Bien sûr, Bundy était motivé dans une grande mesure par des facteurs sexuels, comme on le voit dans ses actes de sadisme, de nécrophilie et de cannibalisme.
Toutefois, le vrai plaisir était d’être maître du destin de la victime, entièrement entre ses mains. Ces tueurs sont plus excités par la vue de leur victime terrorisée et par ses cris, que par le meurtre lui-même.

Un tueur en série peu rarement être “classé” uniquement dans une seule et même catégorie. Le Docteur Petiot, qui tuait principalement pour récupérer l’argent et les possessions de ses victimes, prenait également un grand plaisir à les observer mourir dans d’atroces souffrances.

voilà LE site que je ne cesserai jamais de dévorer ^^

http://www.tueursenserie.org/

What’s going on here?

When trying to open Default Trace files on Windows 7 and SQL Server 2008 I got the “You don’t have permission to open this file” error.  My first and second thoughts were “How can this be, I’m an administrator!?”.  SO the first thing I tried was reading the files using fn_trace_gettable in SSMS.  This works, what is different between SSMS and Profiler?  Nothing that I can think of.

What’s Next?

First step, check permissions on the folder, yup, full control.  Second step, turn off inheritance.  Third step, bang head on desk!  So off to google/bing I went.  I found this post by the SQL Server PSS team, , which told me about the issue, but not a good way to solve it.  I can’t just grant rights to each file because the Default Trace rolls over and creates new files, I need rights all the time.  Then I found this post, which says the owner of the files needs to copy and paste them out to a another shared folder.  While not the most helpful idea for my situation I tried it, and it worked!  I’m still annoyed at this point because I don’t want to have to move the files to read them.

Finally, a solution

Once again it is Twitter to the rescue.  I tweeted my problem and got a pretty quick response from Brian Kelley (Twitter|Blog) asking about OS and if I ran Profiler as Administrator.  I answered Win 7 and Yes, I was mistaken on the Yes it turns out.  I thought because the account I was running under had administrative privileges that I was running as administrator.  This is not the case in Vista, Win 7, and Windows Server 2008 when UAC is on.  With UAC on you still need to run Profiler using elevated privileges by right-clicking and selecting “Run As Administrator”.  That is the answer.  I should also note that Ken Simmons (Twitter|Blog) also produced this answer.   Jonathan Kehayias (Twitter|Blog) also chimed in to let me know that you can set individual applications to always run as administrator by right-clicking, selecting Properties, Compatibility, and checking the Run as Administrator box.  All of this in about 20 minutes and this is after I spent at least an hour fighting with it and searching the internet for a solution!

Conclusion

I really need to get a better understanding of UAC, and believe it or not, Twitter works!

(Denne posten er et dobbeltapropos; til forrige post og til Levende Histories temanummer om Ville vesten.)

Det er laget anslagsvis 2 dusin filmer hvor Wyatt Earp enten er hovedperson eller bifigur. Særlig 7 av dem er verdt å nevne: “Frontier Marshall” (1939) med Randolph Scott, “My Darling Clementine” (1946) med Henry Fonda, “Gunfight at the O.K. Corral” (1957) med Burt Lancaster, “Hour of the Gun” (1967) med James Garner, “Doc” (1971) med Harris Yulin, “Tombstone” (1993) med Kurt Russell og “Wyatt Earp” (1994) med Kevin Costner.

Takket være disse filmene er Wyatt Earp blitt en av de mest navngjetne skikkelsene fra USAs 1800-tall, og mannen er vokst til å bli en metafor/symbol for sterke, ensomme og rettskafne menn som kjemper for å opprettholde lov og orden i Det ville vesten.

Men i sin egen samtid var han en relativt ukjent figur. Det var først etter at forfatteren Stuart Lake i 1931 skapte en myte rundt Earp med boka “Wyatt Earp: Frontier Marshall” at navnet ble kjent. Lake ga Earp helterollen som ensom lovmann i vanskelige omgivelser. Senere filmer benyttet gjerne Lakes bok for å gi seg selv historisk autensitet, men Lakes bok var en salig miks av fantasi og løsrevne fakta.

Virkelighetens Earp var en mann som livnærte seg som gambler og småsvindler vel så mye som lovmann. Han hadde dessuten en bakgrunn som hestetyv og bøffeljeger.

Livet hans var heller ikke så høydramatisk som enkelte filmer vil ha det til. I løpet av sin tid som lovmann i notoriske Dodge City skal han bare ha tatt livet av én mann.

Det berømte oppgjøret ved O.K. Corral varte bare noen få sekunder, og var såpass kaotisk at ikke engang øyenvitnene klarte å bli enige om hva som egentlig hadde foregått.

Så godt som alle filmene er derfor bedre eksempler på mytologisering enn på balansert historieformidling. Men hver av dem er interessant på egne vilkår – siden de sier mye om hvordan ulike epoker forholder seg til samme bit av historien.

Den første filmen om Earp, “Frontier Marshall”, var basert på boka til Lake. Interessant nok hadde regissøren møtt Earp noen år tidligere, og konkludert med at gamlingen var en tvilsom figur. Likevel tegner filmen et skinnende rent helteportrett av ham. Sjangerkravene veide tyngre enn noe annet.

John Fords “My Darling Clementine” gir Earp en mer metaforisk rolle, som representant for sivilisasjonen. Eksempelvis er han ikke bare ute etter hevn. Han ønsker å skape et mer ordnet og trygt samfunn for alle.

I “Gunfight at the O.K. Corral” skildres det sentrale oppgjøret som en paramilitær operasjon som tar hele 6 minutter. Scenen kan godt sies å ha vært skoledannende. Mer interessant er den subtilt homoerotiske skildringen av forholdet mellom Earp og Doc Holiday. Den holder seg på det psykologiske nivået, men er tydelig nok. Den kommer til uttrykk i flere replikker.

“Hour of the Gun” er en problematiserende western. Den begynner med O.K. Corral, for deretter å fokusere på volden som følger i kjølvannet av episoden. Filmen skildrer en moralsk ambivalent Earp.

Denne tendensen er forsterket i “Doc”, hvor Earp portretteres som en korrupt lovmann. Som tittelen antyder er det den tuberkuløse gambleren Doc Holiday som er “helten” her. Begge de to siste filmene er en del av en revisjonistisk tendens innen westengenren, og målgruppen er generasjonen med autoritetsskeptiske 68-ere.

De to filmene fra 90-tallet er svært ulike hverandre. “Tombstone” er rett og slett en moderne actionfilm – ikledd westerngevanter – med høye drapstall og en portrettering av Clanton-klanen som en slags proto-mafia. “Wyatt Earp” er derimot – antakelig – den hittil mest historisk korrekte filmen om legenden Earp, siden den i stor grad tar for seg mannens dårlige sider og skavanker. (Filmens underholdningsverdi er nok mer diskutabel, vil mange si.)

Til syvende og sist må man imidlertid stille et spørsmål om hva slags funksjon en film om en historisk skikkelse skal ha? Skal den etterstrebe korrekte detaljer i størst mulig grad, eller er det sentrale å trekke ut en essens/mening av faktaene? Den første strategien sliter med at alle detaljer og nyanser uansett ikke får plass innenfor rammene av 2 timers spilletid. Og det er en fare for at de detaljene som faktisk blir tatt med kan skape et fortegnet bilde av det som skjedde.

Kanskje det tross alt er bedre å gjøre slik John Ford insisterte på – blant annet i “My Darling Clementine”: Gjør det enkelt, men forhold deg til den overbyggende meningen i historien. Trekk ut essensen.

Det er her debatten har stått og vil stå. Og den vil neppe ta slutt. Problemstillingen blir ikke enklere av at én løsning ikke passer alle prosjekter.