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

  • SEARCH
  • Home
  • 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 311929
In Process

The Archive Base Latest Questions

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

Every time I find out that the performance of data retrieval from my database

  • 0

Every time I find out that the performance of data retrieval from my database is slow. I try to figure out which part of my SQL query has the problem and I try to optimize it and also add some indexes to the table. But this does not always solve the problem.

My question is :

Are there any other tricks to make SQL server performance better?

What are the other reason which can make SQL server performance worse?

  • 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:58:11+00:00Added an answer on May 12, 2026 at 7:58 am
    • Inefficient query design
    • Auto-growing files
    • Too many indexes to be maintained on a table
    • Too few indexes on a table
    • Not properly choosing your clustered index
    • Index fragmentation due to poor maintenance
    • Heap fragmentation due to no clustered index
    • Too high FILLFACTORs used on indexes, causing excessive page splitting
    • Too low of a FILLFACTOR used on indexes, causing excessive space usage and increased scanning time
    • Not using covered indexes where appropriate
    • Non-selective indexes being used
    • Improper maintenance of statistics (out of date statistics)
    • Databases not normalized properly
    • Transaction logs and data sharing the same drive spindles
    • The wrong memory configuration
    • Too little memory
    • Too little CPU
    • Slow hard drives
    • Failing hard drives or other hardware
    • A 3D screensaver on your database server chewing up your CPU
    • Sharing the database server with other processes which compete for CPU and memory
    • Lock contention between queries
    • Queries which scan entire large tables
    • Front end code which searches data in an inefficent manner (nested loops, row by row)
    • CURSORS which are not necessary and/or are not FAST_FORWARD
    • Not setting NOCOUNT when you have large tables being cursored through.
    • Using a transaction isolation level which is too high (such as using SERIALIZABLE when it’s not necessary)
    • Too many round trips between the client and the SQL Server (a chatty interface)
    • An unnecessary linked server query
    • A linked server query which targets a table on a remote server with no primary or candidate key defined
    • Selecting too much data
    • Excessive query recompilations

    oh and there might be some others, too.

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

Sidebar

Related Questions

No related questions found

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.