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 1011395
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T09:13:39+00:00 2026-05-16T09:13:39+00:00

In our SQL Server Database we have at least 25-35 lookup / empty tables

  • 0

In our SQL Server Database we have at least 25-35 lookup / empty tables that are never used. Is there any negative effect for keeping them in our database (performance, storage etc)

Basically, would deleteing them have any positive impact on queries etc.

  • 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-16T09:13:40+00:00Added an answer on May 16, 2026 at 9:13 am

    If queries don’t reference the tables, then there would be no impact to those queries. SQL Server will pay attention to frequently requested information and cache that information in memory. Having a table out there should result in no notable difference in performance or storage.

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

Sidebar

Related Questions

With our product we have a simple backup tool for the sql server database.
On our SQL Server (Version 10.0.1600), I have a stored procedure that I wrote.
I have two tables in a SQL Server 2008 database in my company. The
We have C# entity classes which map to some of our SQL Server database
I have a client supplied file that is loaded in to our SQL Server
Here's task: We have an sql server database. which is hosted at our server.
Our SQL Server 2005 database has nearly 100 different tables. We are going to
I have designed database tables (normalised, on an MS SQL server) and created a
For our SQL Server database, we're using a versioning scheme to track schema updates.
I need to hash (MD5) all the password in our Sql Server 2000 database.

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.