I'd like to host a personal database for about 500 people (1 database per person) on my web server. A person could possibly share their database with a friend or two. On my web server, I'd have some web services, perhaps for doing synchronization, and maybe even an ASP.NET Web Forms front end to the database.
If I restart my IIS web server, would this likely cause database corruptions? Would this be expected to perform ok?
If not Compact, should I instead use SQL Express and create a database in SQL Server for each of my 500 people?
It looks like ScottGu says it's OK:
http://weblogs.asp.net/scottgu/archive/2010/06/30/new-embedded-database-support-with-asp-net.aspx
Related
Forgive me I am not a developer. I have seen tones of post regarding these three little monsters but still get confused in what to use. Here is my use case:
I have a WPF application that runs in client. A location that will have a Master client machines and a few slaves machines containing the same app. The slave applications writes to the master DB through a web service (IIS required). The Master DB will then sync with windows Azure with the build in auto sync feature. Here comes to my questions:
Which DB I should use in order to:
being easily installed in the client, i.e. if you would say SQL Server Express, can we package both IIS, SQL Server Express and my WPF applications into a single package for easy installation in client side?
able to use the Azure auto sync feature - can localDB do so?
license free to the client end users - heard that SQL Server Express has a 10GB limit to the client or otherwise a license fee has to be paid, is that true?
Thank you.
I need to create a website that will display some data fetched from mysql database.
When executing it on my local machine it works correctly.
What i need to know is how do i do this same when websites is moved to the server.I mean i cannot go and create a database for my website on the server.How is this done?
Thanks in advance.
your web host or web server should provide you with PHPmyadmin which allows you to create a database. So if you login on your web host, server you should be able to see phpmyadmin, if you click on that then u are allowed to create a database for your website in your webserver.
I am developing a web app that is not doing anything fancy. The parent company wants to use a cloud based IIS service to support the web app and then submit the information to the client's local SQL servers through the internet and the client's firewalls.
Traffic isn't that much of an issue, we are talking about probably no more than 10 submissions daily per client. My question is with regard to connecting to the client's SQL servers and running the Stored Proc on each server.
We already have admin privileges on the firewalls and servers to do what we need to do to make anything happen.
What would be my best/reliable/secure method to implement this service?
Page asks for 10 items of info then submits to Stored Proc, that's it... with a local IIS server there is no problem, works nice. I want to make sure that the information stays secured, not just for the 10 items, but the SQL server and any security between it and the IIS server.
Any recommendations?
I would recommend setting up a VPN tunnel between the remote IIS server and the in-house SQL server. With a VPN tunnel, the SQL server is just like any other server on the network to the app.
I have a Sproutcore application which uses CouchDB hosted by Cloudant. In devenv I'm using Sproutcore proxy to forward requests to Cloudant (due to single origin policy I obviously can't call a arbitrary hosts from my JavaScript).
What would be your suggestion on hosting the app. CouchApps loading script is failing with obscure error (please note Sproutcore app is around 40 MB of JavaScript and resources).
The thing about hosting an app that talks directly to couchdb is that you are restricted by the same origin policy, so the server that serves up your SproutCore app, has to be on the same domain as you access your couchDB database. If your host provides a static file server, you could use that, but your best bet is probably just to save it as a couch app.
The Key with deploying SC as a couch app, is that you have to set up the URL's that sc-build generates to point to the correct location. This can be done with the buildfile setting something like this:
:url_prefix => '<database>/_design/<designDocument>/'
This way the links point to the right location.
You can also setup CouchDB url rewrites to get simpler urls if you wish. Have a look here for more discussion on this:
https://groups.google.com/d/topic/sproutcore/-D-5T5yPg3A/discussion
PS: 40mb seems overly large! do you have many images? I'd be concerned if you had that much JS/CSS.
Cloudant hosts its clusters (mainly) on EC2 in the us-east-1b or us-west-1b availability zones. If you cannot deploy as a CouchApp you should try to colocate your application layer next to your DB cluster. That will minimize the latency between the web server and the databases.
You can do this yourself by getting an EC2 instance and running a web server on it, or you can use a third party host that hosts on AWS (e.g. Heroku).
In both cases, you will need to run a small proxy from your web server to the database. That's why simply hosting on S3 is not an option at the moment.
Once you deploy your app to a web server, don't forget to check that your web server and your database are in the same AWS availability zone. If they're not, just ask Cloudant to move your account.
I'm working with a client to plan the topology for a public facing SharePoint internet site.
The SharePoint installation will live in the client's DMZ and the plan is to use an existing SQL Server machine to host the SharePoint databases.
The problem is that there is no domain in the DMZ - and the client doesn't want to create one without going through the proper planning process.
As far as I understand, there is no way to configure a multi-server SharePoint farm without using a Domain Account to initially connect SharePoint Central Administration to SQL.
I'm pretty sure (and have tried this) that you can't use SQL Server authentication to connect the farm to SQL Server when first provisioning Central Administration using the Productions and Technologies Wizard.
My other option is a single server install, acknowledging that this limits our future growth if we ever need to add another WFE.
Thank you
No. Mostly.
It is possible because it works this way here in the company I work.
We basically have an user account with the same name on the 2 servers (web front end server and SQL database server). This account has access to the database.