.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
MarieAdela
Imran Ghani
Post New Web Links

Performance degradation using sql client

Posted By:      Posted Date: October 16, 2010    Points: 0   Category :Sql Server
 
We have a SQL 2005 database running on a Windows 2003 Server.  We recently added two new data servers and used Windows 2008 Server.  We have tried R2 and non-R2, plus Windows 2003 Server, on these two new servers, and in all cases performance is so slow as to be unacceptable.  Clients access the data via a Windows 2008 Server running Terminal Services and hit a custom application.  We have tried many different configurations using backup servers, test servers, Windows 7, Windows Vista, Windows Server et. al. - oddly a very old XP client running the application against a 2003 server performs about 7 times faster than either Windows 7, Windows Vista, or Windows Server clients running same.  We have attempted to run the client application compiled under VS 2005, VS 2008, and VS 2010 - using .NET 2.0 to 4.0, under every configuration we can come up with.  What's odd is that neither the client nor the server are taxed for resources.  Memory is fine, processor time is fine, network traffic looks normal.  Any ideas would be greatly appreciated.  


View Complete Post


More Related Resource Links

Video: The Access Show: Client Performance Improvements against SharePoint Lists

  
Today's guest is DJ Cole, architect and primary developer of SharePoint connectivity performance improvements on the Access development team. DJ dropped by to talk about how Access 2010 connects to SharePoint, and to discuss the work necessary for improving client-side performance. (Length: 13:05)

performance degradation...

  
i am using the view as an source: view is created by inner join of two tables. first table that has its created script as : USE [web_master] GO /****** Object: Table [dbo].[Eligibility] Script Date: 08/31/2009 14:06:03 ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO SET ANSI_PADDING ON GO CREATE TABLE [dbo].[Eligibility]( [member] [int] NOT NULL, [parent] [int] NOT NULL, [child] [int] NOT NULL, [effective_date] [datetime] NOT NULL, [termination_date] [datetime] NOT NULL, [bill_indicator] [char](1) NULL, [product_description] [varchar](6) NULL, [location] [int] NULL, [hire_date] [datetime] NULL, [incentive_start_date] [datetime] NULL, [created_time] [datetime] NOT NULL, [created_name] [varchar](25) NOT NULL, [modified_time] [datetime] NOT NULL, [modified_name] [varchar](25) NOT NULL, [Eligibility_id] [int] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL, CONSTRAINT [PK_Eligibility] PRIMARY KEY NONCLUSTERED ( [Eligibility_id] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 100) ON [PRIMARY] ) GO SET ANSI_PADDING OFF GO second tables ahs same conditions as this with different coulmns. Now my query is selecting columns fron the view... If other users also use this view then will it degrade the performance of other users. Than

WPF Performance Profiling Tools for the Client

  
Hi all- Can somebody lead me to a link or explain the difference between some of the leading WPF client side performance profiling tools available?  Our client is leaking memory, and we are trying to find a tool to track it down right now.  Currently, the one I stumbled upon was WPFPerf: http://windowsclient.net/wpf/perf/wpf-perf-tool.aspx   Our company is recommending that we use ANT, and being a GUI developer, I do not know enough to compare / contrast the two products (if one is better than the other for uncovering a client side memory leak / performance issue), or if neither is the best tool for the job, and if there is something better?  Any advice would be great.   Talk soon Chris

Windows 7 SP1 x86, ODBC, and SQL Native Client Performance

  

Good Morning Everyone,

**Reposting to SQL Board. I have this question with Windows 7 Performance as well.**

Since applying SP1 to select Windows 7 Ent machines (testing before mass install), I have found that one of our applications that uses the SQL Native Client for an ODBC connection is awfully slow. It takes 5 minutes for the application to load and come back with initial data load/presentation. I have tried every other SQLCLI install available, including 2005, 2008, and 2008 R2. This was the case when I first tested the application with Windows 7 about 6 months ago until I found driver version 2007.100.2531.0 SQL Server Native Client 10.0, which seemed to resolve the slowness issue. Now, after applying SP1, it has reverted in being slow.

Is there anything I can look for or modify that might be causing this issue? What part of SP1 touched the ODBC or SQL driver?

Regards,

D



D

ASP.NET Best Practices for High Performance Applications

  
This article lists the techniques that you can use to maximize the performance of your ASP.NET applications. It provides common issues, design guidelines, and coding tips to build optimal and robust solutions.

Use jQuery and ASP.NET AJAX to build a client side Repeater

  
By sending only data to the client, you can profoundly reduce the size of what you send and see a substantial increase in performance. You also allow yourself the ability to easily add features like light-weight sorting and paging on the client. This can not only improve your users' experience, but reduce server load and bandwidth requirements.

Client Side Gridview Pagination using JQuery

  
I would like to show how to use Client Side Gridview Pagination using Jquery Table Pagination Plugin by using Ryan Zielke.

Use jQuery and ASP.NET AJAX to build a client side Repeater

  
By sending only data to the client, you can profoundly reduce the size of what you send and see a substantial increase in performance. You also allow yourself the ability to easily add features like light-weight sorting and paging on the client. This can not only improve your users' experience, but reduce server load and bandwidth requirements.

To that end, I'm going to walk you through these four steps to effectively implementing a client side Repeater, using ASP.NET AJAX and jQuery:

Top .NET Performance Problems and how to avoid them

  
Every time I work with one of our .NET customers to help them with managing their application performance I come across the same problems as seen with other clients before: lots of ADO.NET queries, many hidden exceptions in core or 3rd party .NET libraries, slow 3rd party components, inefficient custom code

High-Performance .NET Application Development & Architecture

  
It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. Pre-.NET strategies and design guidelines still effective now were developed with Microsoft's DNA (Distributed interNet Application) platform. This model successfully served the purpose of architecting N(any number of)-Tier (levels) applications. In its basic sense, as in most robust, distributed applications, you'll architect 3 main layers or Tiers: presentation, business rules and data access.

How to improve the performance of ASP.NET MVC web applications

  
It is an in depth analysis of a Digg-like site and how it went from serving (on a test machine) 6 req/sec to 390 req/sec.

The biggest gain, 74 req/sec to 390 req/sec happened when he introduced data caching and another 25 req/sec where gained when he introduced the compilation of LINQ queries.

High Performance ASP.NET - Speeding Up ASP.NET Pages

  
have been writing a series of blog posts, which I have named High Performance ASP.NET Websites Made Easy! There is no rhyme or reason to the order of these posts and certainly can be read in any order:

Developing High Performance and Scalable ASP.NET Websites
Avoid Chatty Interfaces Between the Tiers in Your ASP.NET Web Application
ASP.NET Page Profiling - Page Tracing - High Performance and Scalable ASP.NET Websites Made Easy
Web Applications: N-Tier vs. N-Layer - Benefits and Trade-Offs
Query Analyzer - Sql Server Database Indexes and Execution Plans

Improving Application Performance in .Net

  
Application performance has always been a concern for Web Application developers. This article contains guidelines and tips for maximizing application performance in ASP.NET.

Tips to Improve Your ASP.NET Web site performance

  
ASP.NET has been developed with lots of features which makes developer life easy. Start from ViewState, PostBack, Server Controls , User Controls and etc. All of them can make your web development experience fun and easy, but improper use of them can cause your site performance slowdown. Most of the controls generate overhead to the client and server. Therefore in this article, I I will list out about things you can do and don't to improve your ASP.NET website performance.

Practical Multithreading for Client Apps

  
Writing applications that use multiple threads is often considered an advanced programming task, prone to errors. In this month's column, I'll focus on a practical application of multithreading in Windows® Forms applications with some real benefits, while attempting to keep things simple. My goal is to present multithreading in an approachable way that addresses a very common need: writing applications with a user interface that remain responsive to the user.

10 Tips for Writing High-Performance Web Applications

  
Writing a Web application with ASP.NET is unbelievably easy. So easy, many developers don't take the time to structure their applications for great performance. In this article, I'm going to present 10 tips for writing high-performance Web apps. I'm not limiting my comments to ASP.NET applications because they are just one subset of Web applications. This article won't be the definitive guide for performance-tuning Web applications-an entire book could easily be devoted to that. Instead, think of this as a good place to start.

Use jQuery and ASP.NET AJAX to build a client side Repeater

  
By sending only data to the client, you can profoundly reduce the size of what you send and see a substantial increase in performance. You also allow yourself the ability to easily add features like light-weight sorting and paging on the client. This can not only improve your users' experience, but reduce server load and bandwidth requirements.
Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend