We are developing a disconnected app for some of our tablet users (Windows 8.1) who do field work. We are a WPF shop for internal apps and my design is to use WPF and a SQL server express database that we can then synchronize when a connection is available.
An objection has been raised to this that running SQL server express could affect battery life. Google has let me down here. I am unable to come up with any specs on how running Express may affect battery life. I suppose I could shut the service down and restart it when the app opens and closes, but we will probably be building more of these apps for the tablets and i would prefer to leave it running. battery life is a bit of an issue for our users.
Is there any info out there about how many minutes per day of battery life we can expect to loose just by having SQL express running in the background? My assumption is that it is minimal, please confirm. Are there ways (settings) to minimize its effect?
Related
I experience really slow performance on SSMS (V 18) when connecting to an Azure database (as opposed to an on-premise database)
I get performance issues when using the Object Explorer -e.g. when opening a View definition or opening table Design view. Regular Query performance is not the issue.
Has anyone else experienced this?
What is the solution?
Your Azure database is hosted in the Azure cloud. You are connecting via port 1433 over the WWW. Things like the object explorer are heavy hits on network utilization and things like default timeouts etc. are going to be highly un-tuned to your situation. Some things you could do:
Fire up a VM in Azure, install SSMS, open the firewall ports and see if you experience a lot more performant SSMS features.
Validate, or improve your internet connection. Latency, down/up speed being highly important.
Lastly, as this is likely NOT your main issue, increase your tier level for the hosted database. Assuming this is a hosted database in Azure? The default tier is NOT very performant and if you have a lot of objects it's trying to pop into your object explorer, this could help.
In addition to #maplemale answer - check whether your database connection is set to Proxy or Redirect.
If you can open the 11000-11999 port range in your corporate network then you can benefit from a Redirect connection where your client connects directly to the VM hosting your database rather than being proxied by Azure.
I am creating a website, using mostly html and some php pages, now I have to create a database and connect it with my website, for log in and requests, my question is what database should I go for, is Microsoft access good enough? or sql server or phpmyadmin? the website isn't large, it might get 6 requests per day, I am not a professional programmer but I know a few things about programming, please help
I am an developer in Access. Access technology is a Windows application, not intended for web applications. It is not a back end database which is what a web server needs behind it. The SQL Server - Express Edition (free) would be the product from the Microsoft family. Of course there are other suitable shareware products out there, probably the best known being MySQL.
When the requirement is for internal needs, not public facing, but the users are geographically separated; then Access (and other Windows Applications) are platformed on a Remote Desktop Server (aka Terminal Services).
The other alternative to building your own web application is using one of the database centric web services: Soho, QuickBase, Knack, etc.
I am working on a project where the client is occasionally connected. The client app is being developed in WPF and uses a SQLite database. My plan is to create a central SQL Server database and when the clients connect to a network they can send the data to SQL server.
I have looked at several of the available packages such as Zumero and sql-lite sync but I am not sure if either of them is the right tool for the job.
Just to summarize, my requirements are:
Sync client must work well from within a 64 bit WPF app
Client will need to present a sync status dialog. Perhaps even a conflict resolution screen.
Centralized database will be SQL Server 2012 or greater
Sync framework should provide ability to update schema without minimal effort.
Does anyone have a recommendation of how I should proceed? Your advice is greatly appreciated.
I am hoping someone can help as my knowledge on this is limited.
A client currently has an Access database we designed connected to their SQL Server. When running the database on the same local network it runs fine.
When running the database on an RDC the speeds varies from one office to another. Clicking on a button to open up a form can go from 1-2 seconds to 10+ seconds.
They have 3 remote desktop servers in same location as the SQL server all on the same local network.
I don't believe they have an issue running any other applications on the RDC as the same server is being used by Sage. It is just this access database connecting to the SQL server.
I am trying to understand how the speed can vary so much and determine if it is the Access database or something else to do with the Remote Desktop servers.
I understand it might be a hard question to answer as there are a lot of variables but any thoughts or advice on this would be greatly appreciated.
Thank you.
I have a client with a .Net 1.0 web app that uses IIS and a SQL 2000 database. It is hosted with a shared hosting service and does get not much traffic (a few visitors a day tops). The hosting has occasional downtime, of course, and the client has asked me if I can setup a redundant system to reduce downtime to negligible.
What is the simplest/cheapest improvement I could make to this setup that would satisfy what the client is asking for?
I was imagining hosting the web app and db with 2 different services and adding some logic to the app hand off requests to whichever web server & database are up, but I'm worried about the complexities of keeping the databases in sync.
Is there a better way?
i'd recommend putting and apache2 server with mod_jk in front of the two IIS endpoints.