	[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!

8.7

including decimal point value

Asked by -Dman100- in SQL Server 2005

Tags: sql server

I have the following database table and stored procedure that reads the data from the table (see code below). The real datatype does not allow the value of 8.0. It will always revert to just 8. I can use 8.1, 8.2, 8.3, etc. but, whenever I try to enter just 8.0, the .0 decimal will not be accepted. What is the easiest way to get the .0 decimal point to be accepted. I have other values that do not need to show a decimal point, so I only need to show the .0 decimal point for this one record. There are other records that have 4.7, etc. Then other records with just a whole number value such as 25 without a decimal point.

Thanks for any help.

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:

           
           
             CREATE TABLE [dbo].[customer_service_metric](
	[metric_id] [int] IDENTITY(1,1) NOT NULL,
	[description] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
	[metric] [real] NULL,
 CONSTRAINT [PK_service_report_card] PRIMARY KEY CLUSTERED 
(
	[metric_id] ASC
)WITH (PAD_INDEX  = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
 
 
CREATE PROCEDURE [dbo].[spGetCustomerServiceMetrics]
 
AS
   SELECT metric_id,  description, metric =
	CASE metric_id
	WHEN 1 THEN CAST(metric AS VARCHAR(2)) + '%'
	WHEN 2 THEN CAST(metric AS VARCHAR(10)) + ' seconds'
	ELSE CAST(metric AS VARCHAR(10))
	END
FROM dbo.customer_service_metric

           
         

20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. aneeshatti...1,603,632
2. rrjegan171,513,636
3. angelIII1,457,953
4. chapmandew927,604
5. RiteshShah654,191
6. BrandonG...623,489
7. mark_wills573,509
8. reb73484,935
9. mwvisa1472,716
10. acperkins420,181
11. ralmada387,102
12. CGLuttrell386,285
13. matthews...310,006
14. Sharath_...300,365
15. JestersGrind231,831
16. tigin44219,338
17. pssandhu211,636
18. EugeneZ202,754
19. udayakum...200,308
20. momi_sa...194,257
21. pcelba193,296
22. DanielWilson190,783
23. prabhakar...186,110
24. St3veMax182,397
25. brejk181,029

1. angelIII5,045,718
2. chapmandew3,728,125
3. aneeshatti...2,750,338
4. rrjegan171,513,636
5. mark_wills1,403,775
6. BrandonG...1,324,338
7. mwvisa1920,172
8. acperkins816,148
9. momi_sa...681,226
10. RiteshShah654,191
11. matthews...610,554
12. appari586,119
13. dtodd555,876
14. dqmq547,704
15. ptjcb545,683
16. Yveau539,545
17. DanielWilson521,282
18. EugeneZ502,048
19. reb73484,935
20. brejk449,023
21. PFrog404,802
22. PedroCGD401,974
23. ralmada389,102
24. CGLuttrell386,285
25. imitchie352,938

including decimal point value

Asked by -Dman100- in SQL Server 2005

Tags: sql server

About this solution