Viewing 15 posts - 1,231 through 1,245 (of 1,518 total)
Thanks all for your replies.
This seems to be more of an academic question then.
Cheers!
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 23, 2008 at 9:05 am
jezemine (4/22/2008)
http://sqlblog.com/blogs/adam_machanic/archive/2006/07/12/performance-isnull-vs-coalesce.aspx
but 10% of what? The time your query spends evaluating ISNULL or COALESCE will generally be very tiny compared to the time...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 22, 2008 at 2:35 pm
what's negligible? 1%?
even if COALESCE is 1% faster, having it occur hundreds/thousands of times in frequently run code, should still incur a small overhead, would it not?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 22, 2008 at 2:18 pm
Thanks for the reply.
We actually found the culprit.
It was a monster execution plan that at the point of failure registered over a billion logical reads in Profiler.
We were able...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 22, 2008 at 1:54 pm
riga1966 (4/21/2008)
Hi Mario,So Parent contains the whole text of Stor proc?
Even if it's 3000 lines?
Thanks,
Robert
yes, I believe so.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 22, 2008 at 7:37 am
Perhaps we can request that from Microsoft to include in their next release.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 21, 2008 at 9:46 am
riga1966 (4/21/2008)
Thank you very much for your queries.
They seem to be a much faster way to quickly identify
the most "troubled SQL code" in the system.
Question.
What are the Individual Query and...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 21, 2008 at 8:57 am
Glad it was helpful guys! 🙂
Here is a query to gather useful missing indexes:
--Get missing indexes
SELECT
index_advantage
,user_seeks
,last_user_seek
,avg_total_user_cost
,avg_user_impact
, equality_columns
,included_columns
,[statement]
FROM
(SELECT
user_seeks * avg_total_user_cost * (avg_user_impact * 0.01) AS index_advantage
,migs.*...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 21, 2008 at 8:52 am
An alternative to using SQL Profiler is querying system DMVs (provided your system has been running for a sufficiently long time for enough stats to be collected in memory).
Costliest queries...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 20, 2008 at 1:37 am
A suspended SPID is waiting for a resource (CPU, data from cache) to become available.
For an excellent discussion of this topic I would recommend:
SQL Server 2005 Performance Tuning using...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 20, 2008 at 1:19 am
Are you statistics up-to-date (WITH FULLSCAN)?
Are your indexes defragmented?
Are your queries performing full table scans, where an index would have helped?
These are some of the things you need to be...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 20, 2008 at 12:05 am
If you are referring to the Database-Engine Tuning Advisor (DTA), then yes, that tool has a long way to go to become dependable for index analysis.
However, SQL 2005 ships with...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 19, 2008 at 10:58 pm
After checking the ORACLE installer, found that the provider is already installed.
The issue is caused by missing registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\Providers\OraOLEDB.Oracle
I have manually added this key to the registry and...
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 18, 2008 at 12:16 pm
It looks like we are missing the ORAOLEDB.ORACLE provider. When I check in the registry I do not see it:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\IntanceName\Providers
Any advice on how to install it?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 18, 2008 at 11:06 am
I'm running the following query (on 1 line) and getting same error:
SELECT [col1], [col2], [col3] FROM OPENROWSET('ORAOLEDB.ORACLE','server'; 'user'; 'passwd','SELECT col1, col2, col3 FROM tbl')
Same query works in our test environment.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
April 18, 2008 at 8:28 am
Viewing 15 posts - 1,231 through 1,245 (of 1,518 total)