	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[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.1

Fastest way to get selective rows from a big table?

Asked by JimR123b in MS SQL Server, SQL Query Syntax

Tags: sql, select, stored procedure

We have a large table (over 20 million rows, nearly 8gb in storage size), and we want to select some rows out of it, but only when a field has a specific field value. We're getting the data using a SELECT statement in a store procedure.

Sounds simple enough, but the query is taking so long (presumably because of the number of rows to inspect), that it's unusable for what we want to do with it.

I've attached the code for the creation of the table, and the definition of the stored procedure.

Is there anyway of making this query more efficient?

The database is on SQL Server 2000.

View the Solution FREE for 30 Days

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:

           
           
             GO
 
SET ANSI_NULLS ON
GO
 
SET QUOTED_IDENTIFIER ON
GO
 
CREATE TABLE [dbo].[SynchronisationLog](
	[id] [uniqueidentifier] NOT NULL,
	[orderNum] [bigint] IDENTITY(1,1) NOT NULL,
	[severityLevel] [tinyint] NOT NULL,
	[table] [nvarchar](255) NOT NULL,
	[method] [nvarchar](255) NOT NULL,
	[recordCount] [int] NULL,
	[returnValue] [int] NULL,
	[occuredAt] [datetime] NOT NULL,
	[sessionId] [nvarchar](4000) NOT NULL,
	[src] [nvarchar](255) NULL,
	[desc] [ntext] NULL,
 CONSTRAINT [PK_SynchronisationLog] PRIMARY KEY CLUSTERED 
(
	[id] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, FILLFACTOR = 90) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
 
GO
 
EXEC sys.sp_addextendedproperty @name=N'MS_Description', @value=N'severity level for record. 0 - DEBUG, 1 - INFO, 2 - WARN, 3 - ERROR, 4 - RESULT' , @level0type=N'SCHEMA',@level0name=N'dbo', @level1type=N'TABLE',@level1name=N'SynchronisationLog', @level2type=N'COLUMN',@level2name=N'severityLevel'
GO
 
ALTER TABLE [dbo].[SynchronisationLog] ADD  CONSTRAINT [DF_SynchronisationLog_id]  DEFAULT (newid()) FOR [id]
GO
 
ALTER TABLE [dbo].[SynchronisationLog] ADD  CONSTRAINT [DF_SynchronisationLog_severityLevel]  DEFAULT (0) FOR [severityLevel]
GO
 
------------------------------------------------------------------------------------------------------------
 
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
 
ALTER PROCEDURE [dbo].[TRN_GetSyncSessionLog]
	@SessionID uniqueidentifier
AS
BEGIN
    SET NOCOUNT ON;
 
    SELECT * FROM SynchronisationLog
    WHERE SessionID=@SessionID
END

           
         

20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. angelIII1,341,458
2. aneeshatti...1,133,145
3. rrjegan171,072,477
4. chapmandew766,967
5. RiteshShah729,435
6. BrandonG...626,234
7. acperkins606,988
8. reb73522,425
9. ralmada480,654
10. mark_wills446,542
11. mwvisa1407,463
12. matthews...380,570
13. Sharath_...287,698
14. EugeneZ249,260
15. ScottPletc...222,540
16. CGLuttrell218,953
17. momi_sa...206,089
18. pivar192,087
19. cs97jjm3180,186
20. pcelba174,068
21. pssandhu161,259
22. DanielWilson155,733
23. tigin44153,914
24. rob_farley143,153
25. JestersGrind139,263

1. angelIII12,726,120
2. aneeshatti...5,818,343
3. acperkins4,994,376
4. ScottPletc...4,590,513
5. chapmandew3,340,073
6. arbert2,245,195
7. Lowfatsp...2,174,384
8. EugeneZ1,922,043
9. imran_fast1,485,025
10. rafrancisco1,460,132
11. BrandonG...1,339,712
12. nmcdermaid1,263,861
13. mark_wills1,236,802
14. Hilaire1,221,775
15. matthews...1,181,041
16. Nightman1,158,168
17. bhess11,103,687
18. Mr_Peer...1,087,815
19. ptjcb1,074,620
20. rrjegan171,072,477
21. dtodd1,025,298
22. appari900,309
23. adathelad836,908
24. Sirees776,352
25. RiteshShah729,435

Fastest way to get selective rows from a big table?

Asked by JimR123b in MS SQL Server, SQL Query Syntax

Tags: sql, select, stored procedure

About this solution