Is this considered a "light load" trace to run on SQL Server Profiler This is my first experience of using SQL Server (2012 Enterprise Edition) Profiler. I've set up a trace to log when views are being accessed on a particular database.

I'm running Profiler on my personal PC, connecting to our Live/Production Server and letting the trace run.

It's only monitoring a single database, and writes events when views are accessed (of which there are approx. 300 potential Views in total).

I have reservations that leaving Profiler to run for long periods of time may affect server performance (especially as I'm querying a Live/Production server). 

Is what I've proposed considered a fairly "light load" to be running?
Using Profiler via the UI can cause serious loads on Production systems. What you should bear in mind is that you must always consider using a Server-Side Trace instead of using Profiler's User Interface.

You might think of it as of almost the same. There is very nice article by Gail Shaw that you should definitely read and understand.