I've just started at a new company that is using java and hibernate to
access SQL Server. I tried configuring SQL Profiler to show me what sql
calls are being made to the database and I can't see it.

Can anyone give me some direction? I'm not familiar with hibernate at all.

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erik Sampsell (erik (AT) fuzeboxinc (DOT) com) writes:
I assume you mean nHibernate? No, I don't know anything about it; I've
only heard the name.

But there is no way that nHibernate can call SQL Server without being
captured in a trace, so this is probably something really trivial. Maybe
your filter is poor. Maybe you failed to include both of RPC:Completed and
TSQL:BatchCompleted. (Include Starting as well, in case all batches errors
out.) Maybe you are tracing the wrong server. Maybe the application wasn't
accessing SQL Server while you were tracing.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx