Advertisement

08.14.2008 at 07:30AM PDT, ID: 23648229
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.3

Running the Index Tuning Wizard on linked tables

Asked by afallppl in SQL Query Syntax, MS SQL Server

Tags: , ,

Hi, I have 2 SQL Server databases located on the same machine. I have used Profiler and Index tuning Wizard to create indexes to improve performance. This has worked well except for one instance:-

I have a view in one database (DB1) that fetches data from the other database (DB2). Eg. in DB1 I have a view:
SELECT     DB2.dbo.tblCustomer.CustomerName, DB2.dbo.datOrder.OrderDate
FROM         DB2.dbo.tblCustomer INNER JOIN  DB2.dbo.tblOrder ON DB2.dbo.tblCustomer.CustomerID = DB2.dbo.tblOrder.CustomerID

The problem is that index tuning wizard doesn't seem to include the linked tables, and so the tables in the second database don't get indexed and perform very slowly.

Note the example is a simplified example for clarity. The actual query contains 18 tables.Start Free Trial
[+][-]08.14.2008 at 07:49AM PDT, ID: 22230805

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: SQL Query Syntax, MS SQL Server
Tags: Microsoft, SQL Server 2000, 2000
Sign Up Now!
Solution Provided By: patrikt
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628