query-tuning

In Neo4j (version 3.0), the following queries return the same results: 1. MATCH (a:Label) WHERE a.property = "Something" RETURN a 2. MATCH (a:Label {property: "Something"}) RETURN a While playing with some large datasets, I noticed (and verified using EXPLAIN and PROFILE ) that for some instances, queries like the second one performs better and faster. While other instances exist where both versions performed equally, I didn't yet see one where the first version performed better. The neo4j documentation and tutorials are also divided. There's no explicit comparison between the two. The docs

When executing T-SQL queries via Management Studio, I can use SET STATISTICS IO ON and SET STATISTICS TIME ON to capture statistics for query tuning. How can I gather the same statistics info when I'm using .NET client APIs to execute T-SQL queries instead of using Mangaement Studio's UI? This seems like an obvious thing to be able to do, but after searching MSDN and Google for quite a while, I'm stumped. The closest thing I found was Provider Statistics for SQL Server (ADO.NET) on MSDN, but those stats seem to be client-side stats about network connectivity (e.g. bytes sent/received) from the

I know primary differences between clustered and non clustered indexes and have an understanding of how they actually work. I understand how clustered and non-clustered indexes improve read performance. But one thing I am not sure is that what would be the reasons where I would choose one over the other. For example: If a table does not have a clustered index, should one create a non-clustered index and whats the benefit of doing marc_s I just want to put in a word of warning: please very carefully pick your clustered index! Every "regular" data table ought to have a clustered index, since