Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 311329
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T07:54:53+00:00 2026-05-12T07:54:53+00:00

I have two tables like this. Table A A_ID ( Primary Key) A1 A2

  • 0

I have two tables like this.

Table A

A_ID ( Primary Key)
A1
A2

Table B

B_ID ( Primary Key)
B1
B2
A_ID ( foreign key but not enforced in database, not unique )

Although by default SQL server creates clustered indexes on B_ID, I have lot of select queries on B, which depend on A_ID

something like this

SELECT * FROM B WHERE B.A_ID = ‘SOME ID’

Should I be creating clustered Index on A_ID of TABLE B ?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T07:54:54+00:00Added an answer on May 12, 2026 at 7:54 am

    No a regular non-clustered index should do fine. A clustered index is especially handy when doing range queries (BETWEEN) As a rule of thumb I always create non-clustered indexes on columns used in foreign key constraints.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have two tables, structured like so: table A: A_ID varchar(32) PRIMARY KEY field1
I have two tables in my database that look like this CREATE TABLE IF
I have two tables which looks something like this Table Queue int ID; string
I have two tables Department and Employee . Department table looks like this: ID
So I have two tables structured like so: CREATE TABLE #nodes(node int NOT NULL);
I have two already-existing tables which look (in part) roughly like this: CREATE TABLE
I have two tables like these: CREATE TABLE people ( id INT NOT NULL,
i want to do for a table something like this. I have two tables
I have two database tables: 'MyTable' which has a standard auto-incrementing primary key integer
I have two tables linked by a foreign key. Example: CREATE TABLE one (id

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.