profiler is resource intensive, no matter the SQL version.
there is nothing a slow, resource intensive profiler trace can do that a server side trace cannot do.
EVERY client side trace can be replaced with a low impact server side trace; there are no exceptions to that, because whatever you build as a client side trace can be scripted to be a server side trace template.
for me, running profiler is something i might do if i wanted to do a right now diagnostic, otherwise i'd build the template in profiler and save it as a script to create on the server.
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!