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.
Related
I am using VPN (Endpoint Security, Check Point) to establish connection to the Firebird 2.1 database from IBExpert on my computer. Sometimes I just forget disconnect from database and I cancel/disonnect VPN session only.
When I am connectiong once more to the VPN and database I can see in the mon$attachments that the previous connection/attachment is still existing and its unresolved transactions are causing deadlock errors (that belong to the previous attachment - this can be verified exactly by the transaction number that is reported in the error message of deadlock error).
So - VPN sometimes retains sessions and those VPN sessions keeps the Firebird attachments in existences.
Is there way how can I (using SYSDBA connection) end those other Firebird attachments from my current Firebird session?
I have contacted the VPN administrator to cancel VPN sessions, but it takes time. Database shutdown is out of the question - DB is in production mode. So, ending Firebird attachments using SQL is the only option left for me - if such option exists at all?
In Firebird 2.5 and later, you can delete a connection from MON$ATTACHMENTS to kill a connection. This is not supported with the monitoring tables in Firebird 2.1 as far as I'm aware.
Given even Firebird 2.5 is end-of-life, and Firebird 2.1 has been end-of-life since 2014, you should really consider updating.
Normally, Firebird uses the SO_KEEPALIVE socket option to detect dead connections, but this can take a long time (depending on your OS configuration). An alternative might be to configure dummy_packet_interval in firebird.conf to a non-zero value (the value is seconds, so set it to a reasonable (read, not too low) value).
I have Crystal Reports installed and working against Oracle server. When opening Toad and checking "Top Session Finder" I see that Crystal (cms.exe) constantly has open connections with the database.
Why does cms.exe create so much connections against the database? can it be limited? what is their purpose?
Can I set Crystal Server to open connection only when it needs them and close them when it's done using it?
The cms.exe process stands for Central Management Server, it is one of the core pieces of the Crystal Server platform.
Why does cms.exe create so much connections against the database? can
it be limited?
If you open the CMC (Central Management Console) and select Servers and open the properties page for the Central Management Server, you should see an option System Database ConÂnections Requested.
The option's purpose, explained by the Administrator's Guide:
Specifies the number of CMS system database connections that the CMS
attempts to establish. If the server cannot esÂtablish all of the
requested database connection, the CMS continues to function but at a
reduced performance, since fewer concurrent requests can be served
simultaneously. The CMS will attempt to establish additional
connections, until the requested number of connection is established.
what is their purpose?
Again, taken from the Administrator's Guide:
The CMS maintains security and configuration information, directs
service requests to servers, manages auditing, and maintains the CMS
system database.
In other words: your Crystal Server environment cannot function without the CMS. Shut it down and your whole environment stops working.
It always needs open connections to the database in order to serve requests quickly. While you can limit the number of connection, doing so might impact the performance of your Crystal Server environment.
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
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 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