Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have used fastcgi when a process starts up and then executes and serves results to a client. I used to preload a readonly database into memory during the start up and then use that to server results. The advantage being the data gets loaded and prepared only once and is readily available.
How can this be accomplished in ASP.NET technology without using an external database technology like memcached etc?
It depends on how complicated the database is, but if I needed to do this I would load the database into the application cache as datatables, within the global.asax application_startup method.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
How do I best handle when a user pushing back to a page that is cached with items in a ASP.NET app?
Could I handle the cache with by capturing it in the back buttons event?
There are multiple ways to perform state management in ASP.NET on page navigation. You can use client side state management techniques such as View state , cookies and query string based on your requirement and amount of data you are going to cache.
Please refer below link for complete understanding of caching.
ASP-NET-State-Management
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
When I have a Windows server and I put the results of my most searched queries from SQL Server in a session in a .net application and compared to caching it in Redis, what is the difference or recommended way? What are the implications of putting it in a session in the application?
You question sounds like Session State vs. Redis for storing temporary data.
They are not mutually exclusive. You store Session State in memory on single server.
In multiple web servers in a web farm, we store them in Redis, SQL Server or State Server.
Caching is different. You could read Redis cache vs using memory directly in SO.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I need to implement push technology in my application. I need to display data on the web page as it gets inserted in the database in real time.
I am using ASP.NET MVC with IBM Informix as backend database. I am trying to figure out if it is possible to use SignalR with Informix?
Does SignalR have any dependency on the backend database? Or could it be used with any database?
Signal R is a system for real time (ish) communication over an HTTP connection and your database is for data storage. The two are solutions to completely separate problems, and there is no dependency between them. You can write code to link up these two parts of your application.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I've developed a desktop application(Accountant App). This application is going to import invoices data and do a lot of other things. All data will be stored on remote database (SQL Server). This app needs some 'pre loaded data' to work properly, like a list containing a bunch of cities etc. My question is: Is better to have this data (cities, states, zipcodes) stored in the remote database or is better to use xml, csv files and deploy them with each individual instance of the application? This data will be updated eventually. And this data will be used frequently by the users.
Well you can either use an external file or store them in the database. I think storing it in the database is the better approach since you won't have to distribute another extra file and all of your data will be at one place. Don't forget to seed the data every time you clear the database though.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
We have configuration data stored within the tables like casestatustypes with columns such as statusid, name, description. How to store these kind of data in the web application, instead of hitting the database each time for retrieving the statusid.
You use a technique known as caching. Basically, you build an in-memory copy of the data that you use for retrieval purposes. When you start the application, you pull from the database to create this cache. When you do an insert, update, or delete; you do it to both the cache and database.
Its easy enough to implement yourself, and there are several good libraries out there (Microsoft even has one in Enterprise Library http://msdn.microsoft.com/library/cc467894.aspx).
Gotchas:
If the data set is large, you'll want to implement a caching strategy that doesn't hold the entire dataset in memory (libraries are useful for this).
Since its a web-app, you need to make sure the cache isn't going to be re-created for each session.