We have application sage 300 ERP (Accpac) with SQL Server 2012 Express Edition, this is desktop application.
This application is hosted on a cloud system; they have provided public static IP. Client is working on cloud using Remote Desktop Connection (RDP).
The issue is that when Internet is down then client not able to access application so we have decided to install on his local machine with database.
If internet is down, then he is using local database but client wants if internet is up what he has worked that should be synced with cloud database and what other user worked on cloud that data should be synced. i.e both side data should sync.
Please help me.
Related
I develop a WebApi using a LocalDB, but I want to deploy it to Azure. I found out that you cant use a LocalDB, but you can use a SQL Server Compact.
Is there a way to migrate my old database including the EDMX and all the models to the SQL Server Compact or is there any other approach to upload the application to Azure?
Do the same, but for MSQL, and after use your Microsoft SQL Server Management Studio for your TSQL deployment on SQL Azure.
I found out that you cant use a LocalDB
We can connect to on-premises SQL Server from a WebApp in the Azure App Service using Hybrid connections. There are some snippet from the document. More detail info please refer to tutorial.
Hybrid Connections can connect Azure App Service Web Apps to on-premises resources that use a static TCP port. Supported resources include Microsoft SQL Server, MySQL, HTTP Web APIs, App Service, and most custom Web Services.
As matze supplied link mentioned, we also can publish database to SQL Azure.
This is a really important questions and I would be grateful if anyone can help me.
A developer had developed a service for me which runs in Windows Server. It communicates with sql server database and passes the data to client application. The client application run on windows and communicates with server database using that service. The person had developed two programs coded in C#. One was service which is configured and installed in server and other is a dll that winforms applications uses to get data and perform other functions.
Currently the who setup is working fine. A windows server (2008 R2) is running with SQL Server 2012 (Express). It also has IIS and the service is configured. This is what is present/configured:
Inetpub folder has a folder where service files are present. It has bin folder with dll file and root folder has wcf service file (svc) and web.config file.
IIS has the service configured in application pool and sites
SQL Server is running and SQL Server Management Studio is also installed
The server configuration etc was done by the developer few years ago. Now I wish to shift to another server. So I am trying to configure this in another Windows server (this time Windows Server 2016) and am using Sql Server 2016.
Inspite of me trying to configure the server the same way it is doing in older server (which is running ok) the program is unable to communicate with the new server. I have checked the IIS config, have imported the database in the new server, create users and matched setting. The web config file was tweaked to match new server name. The firewall has port opened. But still it is not working.
I wonder what I am missing or have not yet configured. For e.g. the program uses a port e.g. 1670 and firewall has this port opened but I have not registered this port in new server for WCF. Is this the issue or what? The IIS setting is all done as they match with old server IIS settings.
Please help me in anyway you can. Even when I am trying to run the program locally (on server) to test it, it gives error (network error). The old server (orig) however is working fine.
Thank you.
The problem was solved after I enabled mixed mode authentication in SQL Server. :)
I am creating a window application with a SQL server database. The application need to be installed on a terminal server and other client machine should works with this application.
I have installed this application and SQL Server Express 2008 on server and application worked currently on server but not on client. I got an error on client machine through my application over connecting to the database on server.
Any help is appreciated.
The default installation of SQL Server Express is to allow only local connection.
See this: http://technet.microsoft.com/en-us/library/ms165718(v=sql.105).aspx
I have a corporate client server application. It passes majority of the work from the client application (Windows 7) to the server application (Server 2008 R2), and when it comes to running a SQL query (SQL Server 2008), it is handled by the server - which registers the user as the server.
We then have a table in our database which is locked down using Active Directory.
Our client and server are written in .Net 4.0. I'm Using WCF (net.tcp).
How would I pass the logged in user security token from our Windows 7 client, to our server in order for the server to turn around and use it to connect to the SQL server to run a couple of quick queries.
Any thoughts, or ideas, would be greatly appreciated! Thanks.
You might want to create a service account for SQL server access.
You can impersonate/change identity in your windows application using the service account before making a call to database. so while database call is being executed it will run under impersonated identity(service account). For impersonation in windows application see this MSDN Article
What you are talking about is the double hop scenario. Check out this SO question regarding how to set up double hop possibilities.
I am working on windows forms application using c#.net. i have developed an application(3-tier) that uses sql database as backend. i need to deploy the database on server and my app. on client machine. but how could my application communicate with database on server. please guide me.
you need a connection string that works fine during development. On your development machine if the application is connecting fine to the database server, chances are that on your client machine, it would work as well. Sometimes, the problem occurs with the credentials that you use, that might work on the development machine but on the client it wont connect due to the lack of access rights. so you need to make sure that you give proper credentials to connect to the SQL server
You don't need to do any rocket science for this. All you need to do is on the client side use the proper connection string that can connect to a remotely installed SQL Server.
Use EntityFramework for your sql server connection for updating, inserting and deleting.
Use storedprocedures for the insert/update/delete functions.