I developed the Windows Application using Entity Framework 4.0 with SQL Server. In development the SQL Server has been installed in local machine it self. While moving production my client wants to deploy the SQL Server in remote location, the insert/update operation is taking bit more time in Remote Server but it executes very fast if it is local server.
Please guide me how to improve the performance?
The problem may be caused by network problems or something with the SQL Server, to rule out either the SQL Server, you can use the Profiler and look at the times and others.
Regards
Related
I have a production server with transaction replication in place. I am only migrating the publisher server to a Windows Server 2012 for TLS 1.2 compliance. The SQL Server version is staying the same: 2008 R2. The distribution server and the subscription servers are not being moved. I have one subscription server with 48 separate subscriptions.
I need to find out what is the best way to deal with the replication. The new publication server will not have the same name. So what changes do I need to make on the distribution/subscription servers? Can I generate the script out on the publication server, run it on the new migrated server? I have been discouraged to do the system db restores on the new servers. So I am restoring the publisher databases on the new migrated server. Do I need to do the subscription database from scratch or leave it as is, and once I run the scripts on the publisher server and change some settings on the distribution and subscription server, it will catch on? I'm not sure. Please help if you can. Thanks.
I have installed a SQL Express 2008 Server on my Desktop for some local work. This has mixed authentication. I have enabled TCP/IP connection so that one colleague can connect to this server. However, this exposes the server to everyone in the network. How do i keep track of which PC in the network connected to this server and when ? This would just help me audit the usage of the server.
Well you can get information about current users, sessions, and processes in an instance by using
sp_who;
MSDN Documentation
I have successfully deployed Google Cloud SQL with phpmyadmin running on App Engine. When connecting the database directly using App Engine the performance is fine but while connecting it via sql client or external server it takes too long to load.
Can anyone tell me what might be the reason for this behavior?
We have an SSIS package running inside a SQL Server 2008 environment.
The package is supposed to transfer data to a SQL 2012 table.
The package however often encounters the "TCP connection forcibly closed by remote host" or "Communication link failure" errors. And when it successfully completes, it runs in 4-5 hrs,
which does not happen to other packages.
Resources/resolutions on the web seem very specific to their issue.
Is this problem related to environment of the destination being SQL 2012?
Or can this be solved by disabling priority boost in the 2012 server?
Any help would be greatly appreciated. Thanks.
Perhaps you should try to establish the communication between the servers using the SQL Native Client [Named pipes] provider. You can set up the communication channels using the Server Configuration Utility.
HTH, let us know !
Greg.
I was using MySQL Workbench and I am not able to figure out the difference between the following:
1. Server instance
2. Connection to server
In general I want to know if we can use Open Connection to start querying without creating
a server instance of the connection we are trying to connect. Are these two things independent?
You need one or two connections depending on what you wanna do with your server. For MySQL work (i.e. running queries) you need a MySQL connection. For server work (e.g. shutting the MySQL server down or manage other aspects that require shell access) you need a second connection (which is called a Server Instance).
Beginning with MySQL Workbench 6.0 we merged both connection settings into one interface.