Architecture :: Design An Application To Fetch Data From Different Application Databases
Nov 10, 2010
I need to develop an application, which will get records (orders) from one application and process them. The updates to this records (order updates) will be sent back to the source application for end customer reference. I'm planning to achieve this data synchronization at the database level using triggers and stored procedures to insert database between the 2 databases.
But, the issue is I have to deploy this application in 3 different customer sites and I have to change the database names (cannot use the same database name) in each deployment manually. Because of this deployment issue, I was thinking of handling this within the asp.net application where I can store the db name in the database and then build the query within the application, but I dont want to do it as building queries like that doesnt look very professional.
I am supposed to develop an enterprise-class ASP.NET Web Application that connects to multiple databases. For example when the web form loads, I should populate different ASP.NET controls (GridView, DataPager, TextBox, DropdownList etc) from multiple databases (SQL Server, Oracle, DB2, SAP Server etc) and also, edit the data in the controls and save the data to the respective databases on button submit.
Should I use Web Service or WCF for data integration, if so is there a limit on the size of the data?
What should be the architecture considering the application should be scalable and easy to maintain?
I have an application that allows admins to add types such as document types and training types that are in seperate tables with a foreign key in a transaction table.
When structuring my class I decided to go with an abstract-like pattern (without the factory methods though). So I have a Type abstract class that defines my Save, Delete, and GetList methods. I have a training type class that inherits this class. The thing is all types have 3 main properties - defined in the abstract base - but have different source tables and thus different store procedures in my DbCommand object. So basically I repeat setting up the same parameters on all the derived classes. I would like to implement the common stuff in the base but I am getting thrown off by the difference in data sources.
Am using two web application and one web service. My doubt is, am sending the dataset from my first application to Web service. After sending the dataset to my web service, i like to fetch the dataset using second application from the web service. How shall i fetch the dataset by using second application.
1) sending the dataset from first application to web service. 2) web service receives the dataset from the first application. 3) second application want to fetch the dataset from the web service which was sent by first application.
I need to auto update application like in wordpress, Application must check if new updates are available, download this updates and install.But I don't know how to install application. Because if some files in bin directory are updated application is restarted.Is it possible to create ASP.NET web application which will be auto updatable?now we have a new technologies, could u please suggest me any kind of soultion for the above problem. here i am enclosing my email email@example.com
can't connect to sql 2005 express sp1 and vs is also sp1. 2) Which my guess is because of the database connection not being able... design view is not able to pull in the application for design, it's as if there is no theme and css just white background and black print.
I've got a web application with 3 layers: front, business and data. I'm using linqToSql for retrieving my data from the db. On the front end, I'd like to show the data that's being pulled from the database. In online examples all code is shown in the same layer. I'm wondering if it's good design to put a reference to the linqtosql classes in my front end so I can bind the results to my gridview, or whether I should use a different way. Since the user should be able to update the data, the easiest thing would be to use the gridview, connect it to the linq2sql datasource and bind it that way, but that would totally defeat my 3-layer structure.
I'm about to begin designing the architecture of a personal project that has the following characteristics:
Essentially a "game" containing several concurrent users based on a sport. Matches in this sport are simulated on a regular basis and their results stored in a database. Users can view the details of a simulated match "live" when it is occurring as well as see results after they have occurred. I developed a similar web application with a much smaller scope as the previous iteration of this project. In that case, however, I chose to go with SQLite as my DB provider since I also had a redistributable desktop application that could be used to manually simulate matches (and in fact that ran as a standalone simulator outside of the web application). My constraints have now shifted to be only a web application, so I don't have to worry about this additional level of complexity.
My main problem with my previous implementation was handling concurrent requests. I made the mistake of using one database (which was represented by a single file on disk) to power both the simulation aspect (which ran in a separate process on the server) and the web application. Hence, when users were accessing the website concurrently with a live simulation happening, there were all sorts of database access issues since it was getting locked by one process. I fixed this by implementing a cross-process mutex on database operations but this drastically slowed down the performance of the website. The tools I will be using are:
ASP.NET for the web application. SQL Server 2008 R2 for the database. probably with an NHibernate layer for object relational mapping. My question is, how do I design this so I will achieve optimal efficiency as well as concurrent access? Obviously shifting to an actual DB server from a file will have it's positives, but do I need to have two redundant servers--one for the simulation process and one for the web server process?
I m sure this question has been asked before. I have a web application hosted underhttp://localhost/abc. which is mapped to c:inetputwwwrootabc folder. I have APP_Code, App_LocalResources, BIN and other folders under abc folder. Everything is great. Now I want to create another application or sub application http://localhost/def. Both abc and def apps need to use some common classes and resources. Whats the best way to do it. I dont need to create a separate application for def. All i want is the url http://localhost/def.
i am new in asp.net. i have create a website. its related to tours and travels. Now when any customer get login to webportal then the login info of that customer should send to my system i.e. website. here it will check the user is valid or not or new according to that check user's permissions and send the data to the webportal.
the best practice for a designing a simple CRUD application with some screens updating various tables (like admin pages to maintain static data for an application). the simplest way would be to drag a data grid/gridview, bind it to a dataset and use a data adapter for CRUD operations. but if this application needs to be scalable, lets say to add any extra UI/business logic in future, then is there any design pattern that can with this? should I be using an object data source control and bind it to business objects instead? or are there any better ways of doing it? should I build a complete layered application or will that be overengineering for this requirement?
I'm thinking of using 3 layered architecture in my web site.Kind of classic layers - Presentation, BL, DAL and BO - business objects, just like in this great article http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=416I will have 4 projects according to levels.I'm goung to store data in xml files and my question is where should those files be located? In App_Data folder of web site? Then how DAL will know path where to find files to parse?
Say you have a form designed in Silverlight(Front end)-Asp.NEt(business layer)-SQl(bakcend)Should data validation occur on all 3 layers or just the presentation layer or a combination of the front end with the other 2 e.g. validating an email address? I'm trying to undestand as to why if data has been validated on the presentation why further data validation would be necessary especially if there would be large amounts of data being validated and this could potentially slow down database transactions?
Then I have prepared a model,controller,view for accessing and displaying the data. I am using LINQ o get the data from database but getting the exception:" A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)" I have also installed the MYSQL connector. provide me the solution to access the data using MYSQL and LINQ in MVC application
My requirement is, to open existing .xls template, write data to some specific /fixed cells to it and make it available for download.In case if I will use "Excel.Application", then at the time of deployment is it necessary that Server should have Microsoft Office installed?
I am fetching data from oracle data base in asp.net application. To achieve this functionality i have used Oracle.DataAccess dll . In my developement enviorment it working fine.
But once I deployed this code on IIS 6.0 it is stopped working and I checked my log and found connection not get established . Then I make sure Oracle.DataAccess.dll present in to bin folder also I try to put this dll in side GAC, but still my code is not working on deployed server.
I am working with a financial application and am looking for the best solution for designing my application.
We have 100's of stored procedures where most/all of our business logic sits. We have WCF web services projects built using Web Service Software Factory (http://servicefactory.codeplex.com/). We have stored procedures built for nearly everything (tables, dropdowns, etc..) and each of these stored procs have their own webservice exposed to be called by the web application. Each web service is a very simple method that calls the stored procedure with the exact paramaters of the web service. I am not too sure if this is the best design and would like to ask for suggestions and alternatives to the design. Does anyone else have a similar environment ? How is it implemented on your end ?
While designing (and then implementing) a layered application:
Is it correct to use the same ORM objects accross all layers? (which would go against encapsulation).
Or the presentation, business and data layer should each have their own objects? (which would lead to lots of code repetition).
e.g. (just to illustrate the question): if one uses Linq to SQL in the Data Layer and Visual Studio's O/R designer to generate the ORM objects, are those objects supposed to be used in the Business and Presentation Layers as well.
i.e.: Are the objects associated with the entities that the application handles a crosscutting issue?