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 5 years ago.
Improve this question
I am creating a library web portal for various colleges, for now I am using a single database for all colleges. I am confused whether to use separate databases for each college or not. Because for now there are 7 colleges using that web portal, but in the future, if there 100 colleges using that web portal, all of them having millions of records in the database.
I would say, stick to that single database for now. In future if that database contains millions of records, you don't need to worry.
You can migrate the data from that database to another one using the method Database Replication.
For more details: https://learn.microsoft.com/en-us/sql/database-engine/database-mirroring/database-mirroring-and-replication-sql-server.
If you want to transfer between two servers like taking backups and restoring to the database on different server, you can use the method -Transaction log shipping.
For details: https://learn.microsoft.com/en-us/sql/database-engine/log-shipping/about-log-shipping-sql-server
Related
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 1 year ago.
Improve this question
Firestore lets you choose geographic location for database I think I am in India and choose relevant location for my database. The queries or reads are much faster. Now the question comes here I am building an app for globe. In that can I create multiple Firebase/firestore projects and linked them with one app is it good idea to do. Is it possible to linked it with flutter somehow or having multiple Firebase projects for one app is a problem for Firebase or play store
I don't think using multiple projects for a single app is great idea as you'll have to replicate the data across them. I personally haven't encountered any major difference whether I use any region in US or in Asia. It's usually a few milliseconds at max.
However, if most of your users are in India and then you should probably consider selecting any region in Asia. If you need more availability then you should consider any multi-regional location (only 2 are available at the moment i.e. US and Europe).
You can initialize multiple Firebase projects in a single application but as mentioned earlier you would have to figure out the region (or project) closest to the user and then connect to that specific project and also replicate the data in both which I'm not sure if is worth doing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
If we have an ASP MVC4 web application and we have to provide it to multiple companies with their logins, what should be the best way with respect to database architecture.
Should we make separate dbs for each company and on url bases we will connect with respective database?
Or should we make one db and use a key for each company?
Because each company will be using the same web application but with its own records.
I am still confused about it because if we make separate dbs for like 100 companies and we need to change a column or cell of db or we want to do updates in our software we will have to change it in 100 dbs. So is there some way Microsoft provides for SQL Server 2008R2.
Thanks for help in advance.
As shown my practice, often different companies wants different functionality or additional features for some parts of web-application. So better will be to separate not only db but web app also.
Also question is it intranet or internet solution? If intranet - no questions. If internet -use third level domain name and separate db for each company. It will give you more flexibility.
This is not as simple to answer as it sounds as it depends upon exactly what you are doing.
Microsoft have quite a good paper on this which I strongly recommend you read before you start. http://msdn.microsoft.com/en-us/library/aa479086.aspx
At our firm we use one database for each client and a main database to keep track of which databases we have and what server they are on. We also have a couple of other databases for aggrigated reporting and keeping track of background processes. We only have one web site accessing those databases which works well for us.
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 9 years ago.
Improve this question
I need to create my own application that is similar windows performance monitor. I want to monitor the DQL using asp.net. But i don't know where to start. I already research but no luck.
Consider using below components (but still remember, it is only a suggestion) to start from:
System.Diagnostics.PerformanceCounter class - to access performance counter data
ASP.NET MVC - to create a website
SignalR - to create a backend Hub for client notifications of data gathered by PerformanceCounter class
DotNet.Highcharts - to create charts control
What is your planned usage of this application? If you are planning to use it for your organization then you might want to consider SaaS solution that allows you to plug in your collector.
You have better uptime on the monitoring application because that monitoring service is the last thing you want to go down. You are probably more familiar with how to monitor DQL than to create an application that does charting and alerting. You should be able to get something going within days instead of weeks.
Monitoring is normally composed of collecting, storing and charting. A good SaaS monitoring tool will do well with storing and charting and you need to look for ones with plugin framework that allow you to decide what to collect.
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 7 years ago.
Improve this question
We are converting legacy VB application to ASP.Net application.
We have the several word documents stored in SQL server database.
Users should be able to edit the word documents and store it in the database.
I am trying to use iFrame whose source would be the word document in the server.
Users will have MS word installed on client PC but not on the server.
But how can i get the changed file in ASP.Net and store it back on the server.
Please advise me.
Regards,
Mugil.
If you want to edit documents in MS Word and store them online, you probably have to write a plugin for Word. A simple and crude solution would be to require the users to save the document locally and then upload it via your website.
You probably want to take a look at Sharepoint.
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 3 years ago.
Improve this question
Has anyone connected the R package to QuickBooks? I know there is an ODBC driver than can be bought. Just wondering if anyone has already gone down this road.
Any insight will be much appreciated!
~ Brock
Google QODBC. It allows you to access Quickbooks via ODBC.
However, it works through creating an interface to XML files. For large QB files it can be painfully slow if you don't properly use indices and limit the data to exactly what is necessary. It's also very quirky. Lastly, not all tables are exposed (Quickbooks fault, not theirs) such as some payroll tables.
What I often ended up doing for large QB files is exporting the data at night via the QODBC driver into a sql database so that ad hoc analysis could be run quickly without compromising the performance for QB users during the day.
Good luck!