Post New Web Links

Why does it takes such a long time to load a parameter?

Posted By: Posted Date: September 10, 2010 Points: 0 Category :Sql Server

Hi all, I have a parameter which is filled with a set of about 90.000 rows. When running the report, it takes a long time to view the report. While it loads the report the CPU on the client is getting up with 50% and the memory stacks 300 MB. I think that I am doing something wrong as when I run the query directly at the cube, it takes just 9 seconds. Does anybody have coped with this problem? If so, what are the best practices in this? Your help will be greatly appreciated! Daniel

View Complete Post

More Related Resource Links

WorkflowApplication.Load takes a long time

When I load a persisted WF instance, I can watch a profiler of the DB activity. From the time I step over .Load until I see the LoadInstance stored procedure execute is taking anywhere from 5 to 10 seconds. Is there a way to alter this behavior?

Here is how I am creating the Instance Store:

 public class WorkflowLoader : IDisposable
 {
  public SqlWorkflowInstanceStore InstanceStore { get; private set; }
  InstanceHandle mInstanceHandle;
  private string mConnectionString;

  public WorkflowLoader(string connectionString)
  {
   mConnectionString = connectionString;
   Open();
  }

  public WorkflowApplication CreateInstance(Activity activity, IDictionary<string,object> inputs)
  {
   //
   // if we dont have an instance store, then we have been disposed already
   //

WCF Service: takes very long time to start up

Hi, What could be the reasons, why my WCF service takes up to 40 seconds to get started? My service class is set to [ServiceBehavior(InstanceContextMode = InstanceContextMode.Single)] I am running a thread inside this class. The WCF service gets initialized and opened within the context of this thread. The Initialization: private void InitializeWCFService() { // initialize servcie base addrresses this.SetupBaseAddresses(); //MetaData behaviour : allow HttpGet ServiceMetadataBehavior metaDataBehavior = new ServiceMetadataBehavior(); metaDataBehavior.HttpGetEnabled = true; // initialize service host instance this.seviceHost = new ServiceHost(this, this.httpBaseAddress, this.tcpBaseAddress); // add service endpoints and behavior. this.seviceHost.AddServiceEndpoint(typeof(IUpdateServer), this.GetServerBinding(BindingType.Tcp), EndpointName); this.seviceHost.AddServiceEndpoint(typeof(IUpdateServer), this.GetServerBinding(BindingType.Http), EndpointName); this.seviceHost.Description.Behaviors.Add(metaDataBehavior); // MEX endpoint this.seviceHost.AddServic

Closing a WCF connection takes a long time when using SSL

I have a very puzzling problem closing WCF connections. We utilize several different protocols for different customers. The most common is net.tcp. We now have a customer that requires SSL encryption of their WCF calls. It does seem to work, but exhibits some strange behavior when we close the connection.

Closing the connection takes a long time. This could be caused by any number of problems, but the strange thing is that the more data that was transmitted on the connection, the longer it takes to close. Connections that get a small amount of data close reasonably fast, but if a large amount of data was transmitted, closing the connection can take as long as actually retrieving the data. It almost seems as if the data is being retransmitted back to the server for verification before the connection is closed.

We are using reliable sessions and Binary over HTTP protocol.

SSIS - OLE DB from VIEW takes long time

Hi,

I have a question regarding SSIS 2008 and how it handles views. I hope the answer for this question will be a quick "Get a hotfix" heh.

I am experiencing a very odd behavior with setting up a View as a data-source in OLE DB. I have set up a a very simple package (for experimenting) with a Data Flow Task that has only two components, Data-Source and Data-Destination. I have set the data-source to a view and the destination to a table in the same database.

Note: I am developing the package on the server itself.

Issues:

While trying to preview data-source I get an error, "Query Timeout expired (Microsoft SQL Server Native Client 10.0)
When executing the package Validation, Pre-Execute phases are complete but no rows are passing through the buffer. I have waited over 12 hours before stop the job. Checking the monitoring verified that IO was on 1. And that no object was locked , which may have caused the package to run so long or not to retrieve data.
When connecting to SSMS and doing export of data from the view - it also retrieves no data and the process seems to be stuck.

Additional data:

first login takes a long time

hi all,

i have set up a moss site, and i notice an interesting thing that the first login of every day usually takes a long time, while subsequent logins of the same day take much less time. what could be the problem? is it related to caching behavior?

any suggestions on how to improve the response speed?

thanks

Andrew Chen
BI, Data Mining, Analytical CRM

Why WPF bug fixes takes so long time?

Hello!

Why the feedbacking takes so long time to get official comments? I'm not speaking about getting the issues to be fixed as it takes even more.

The perfect sample:

http://connect.microsoft.com/VisualStudio/feedback/details/483010/wpf-gridsplitter-randomly-jumps-when-resizing

It is a known bug for a three years (there is a link to a first discussion in a feedback comment), and the offical answer is:

Posted by Microsoft on 8/21/2009 at 2:35 PM
I do understand your concern, but we are beyond our ZBB date, therefore only ship-blocker bugs make the bar at this point. Considering that we have shipped this bug before, it is hard to make a case that we need to fix it in this release since it did not block our previous release. Thank you.

So, the official policy is "Now, we have a six months before RTM but we will not fix any bugs but those that blocks tth product shipment"? Perfect!

I've a bunch of bugs/suggestions submitted and (for most of them) there's no single comment neither reaction for a six month for now. I'm

SqlCeConnection.Open() takes very long time

SqlCeConnection.Open() takes very long time if the sdf file is more than 300MB, actually, SqlCeConnection.Open() will not response in Windows Mobile 6.5 device, but it works in Windows 7.

string connectionString = @"Data Source=\Navigator\tnmsdb_DISTRICT-00001-00008-00017.sdf;Max Database Size = 280";

huge number of data from database ... so how to minimize load time

Hi ...

I have used the above method to configure my crystal report ...

Its working fine , But i have huge number of data in database ....

So , it take long time to load the report ...

So , i have decided to show only the last 50 records inserted into the database , not all the 500 records to be loaded every time.

Plz help me with this issue ...

Also , Plz explain me abt index legend in crystal report.

Under the Hood: Optimizing DLL Load Time Performance

Matt Pietrek

MSDN Magazine May 2000

Slow page load during a list query one time during the day

We have a monitoring tool set to check to see if the home pages for our 3 web apps load in under 60 seconds every 10 minutes. All 3 web apps load in under 3 seconds on every 10 minute check except for one exception. One check every day one of the web app's home page takes longer than 60 seconds to load. This happens at 11:45PM when there is very little user usage on the environment. The characteristics of this page are as follows: The only thing on the page is a list view web part which was added by the browser. The page has not been customized with SPD or code at all. The list that it pulls is a simple links list that has 281 items on it. The view pulls all 281 items and displays them in sets of 100. I cannot find any associated event in the server events and/or SharePoint ULS logs nor are there any daily sharepoint timer jobs running at that time. Our full index happens at midnight with incremental happening hourly. Our enviroment is 2 WFEs, 1 App/indexer and we have a separate SQL cluster backend.

Could someone lead me possibly in the direction I should take next in my troubleshooting?

STSADM ActivateFeature takes too long

Hi,

I have a solution installed to a web application, this Web App has a lot of Site Collections, these site collections were created with different versions of the wsp package. What I need is a way of activating the new features on the already provisioned site collections.

At first we made a Web Application scoped feature that went through all site collections that were using our template and then activated the features on each site collection but it was giving us a whole bunch of trouble were the code would skip entire site collections or enter the site collection, changing a field that we used for control and not activating anything... Now we have a Web scoped feature that activates all the features within the site collection at either Web or Site scope that we specify through an XML. This works like a charm for every site collection.

The problem is that we need a way of activating that feature on every site collection so I did a batch file that runs the STSADM ActivateFeature to do this. This also works properly but seing the many site collections that we have it is taking more than an hour and a half to finish the batch; is there a way of optimizing this so it runs quicker?

I think that the batch is actually waiting untill the feature is done activating to start to activate the feature on the next site collection, is there a way of a

Slow load time of custom assembly on x64 compared to x86.

I am developing an application that automatically generates assemblies using the CSharpCodeProvider (.Net Framework 3.5). These assemblies contain a single class with a very large number of local variables and methods. After compilation I create an instance of this class (using Activator.CreateInstance) to be used elsewhere in the application. When the application is deployed on a 32-bit system (tested on Win 7 Prof 32-bit and on Win XP) the CreateInstance method returns after 1 or 2 seconds, i.e. it first JITs the assembly before creating the instance. However, on a 64-bit system (tested on Win 7 Home 64-bit, Win Server 2003 64-bit and Win Server 2008 64-bit) CreateInstance takes up to 5 minutes to return. Is there any reason why it would be that much slower on a 64-bit machine? I have tried many different options when compiling, such as setting the platform to x64, using the /optimize flag, etc, but none of these have made a difference. I also tried calling PrepareMethod on all the method in the class. When I do this in the 32-bit environment, it takes approximately 10 seconds. In the 64-bit environment it takes more than 3 minutes. As a last resort I tried ngen before constructing the object, but this made no difference in the execution time.

SP Datetime parameter requires time input

I'm working on a Crystal report that contains 4 subreports. Each subreport passes 2 date parameters to a stored procedure. This works, but only if a value for time is also entered in the Crystal parameter prompt. How can I fix the stored procedure so these parameters will accept only a date as input?

Does SQL Server have to load and init statics every time a SQL/CLR managed proc is invoked?

We are working with SQL/CLR stored procedures, triggers etc and it seems that all assemblies we use are unloaded/loaded every time a proc or trigger or TVF is called. Is this true? Is there any way to retain data between invocations of procs? for example can I create some static struct or object that I can setup once and then just refer to after that, so that unless we terminate SQL server, the static data is always in memory? Thanks PS: This was originally posted here, but that forum seems to be rarely frequented.

WCF - First call to Callback instance from Server takes considerable time to make it to the client.

Hello. There's a performance problem we are facing that we are unable to fix using DuplexChannels. The first call made by the client to the server reaches the server instantly. The first call made by the server to the first client using a Callback proxy will take several seconds to reach the client. All subsequent calls to the client (as well as other clients) will reach and execute instantly. The client connects to the Server using a proxy to IServiceProvision, supplies an instance to an implementation of IClientCallback and calls IServiceProvision.Start(). The server instantly processes the call and makes an asynchronous call to IClientCallback.DoWork(), which takes several seconds to enter the client's DoWork() implementation. The remainder of the execution then runs smoothly. Also, the server will experience such a slowdown only for the very first call of the first client that connects to it. Is it normal for the Callback interface to take so much time to warmup, only on the first call to the first client? Below is the full source code. Thanks for any information you may provide. Cheers Mike Shared Class Library using System.ServiceModel; namespace Test { [ServiceContract(Namespace = "http://test/IService", CallbackContract = typeof(IClientCallback))] public interface IServiceProvision { [OperationContract] void Start(); [OperationContract] void

SQLDataAdapter/SQLDataReader takes lot of time for executing a query

All, I have a webpage with 6 drop down lists. User can start with selecting any drop down list first, and then proceed in any order. 1. Assume when the 1st dropdown is selected first, rest 5 drop downs (except 1st) are filtered/updated based on the selected value in the 1st dropdown. 2. Assume user selects the 4th dropdown second, rest 5 drop downs (except 4th) will be filtered/updated but the condition would be based on both 1st drop down and 4th drop down. But while filtering the first drop down, only the 4th drop down is used as filter (self-filter will be ignored). The code works fine but I see a very bad performance hit in time when the user selects the fourth dropdown after selecting three drop downs. I tried using both SQLDataAdapter and SQLDataReader but neither used to solve the issue. The code takes a lot of time on one line in either of the code (which is highlighted below). When I run the query in SQLServer Mgmt Studio, the query completes in a few seconds.Using SQLDataReader: SqlConnection conn = new SqlConnection(CONNECTION); SqlCommand ObjCmd = new SqlCommand(query, conn); ObjCmd.CommandTimeout = 600; conn.Open(); SqlDataReader daSelTools = ObjCmd.ExecuteReader(); //This line takes a lot of time ddl.Items.Clear(); // Call Read before accessing data. while (daSelTools.Read()) { ddl.Items.Add(new ListItem(String.Format("{0}",daSelTools[0])));

Is there a function in Jquery which run only one time no matter load page or PostBack

In asp.net, I can use Method A to run somethings A one time, and somethings A will nor run when page is postback but In JQuery, I hope to run something B one time when the page is loaded, but if I use Method B, the "Somethings B" always run even the page is pastBack, how can I do? Thanks! ------------------Method A------------protected void Page_Load(object sender, EventArgs e){ if (!IsPostBack) { //Do Somethings A } } ------------------Method B------------$(document).ready(function () { //Do Somethings B})


Categories:

ASP.Net	Windows Application	.NET Framework	C#	VB.Net	ADO.Net
Sql Server	SharePoint	Silverlight	Others	All