Enterprise Manager Hanging When Removing Replication
Aug 29, 2007
I'm trying to remove replication from my database so that I can run some update scripts on it but SQL Enterprise Manager just keeps hanging on me. I've searched the web an no-one seems to have had this problem.
Does anyone know of this problem or have they experienced it? If so, can you help?
Am I doing something wrong trying to remove the replication (deleting the publication)?
Hi guys does anyone know of a quick solution to remove the replication monitor icon within Enterprise Manager please I have tried all sorts but it is still appearing and starting to irritate me as I don't use replication on this server. cheers
Hi all, I have a replication that worked for a couple of weeks without any problem. Since yesterday it is hanging. I am not aware of any changes done to the network or dataservers. Dataservers are on 2005 SP1. In the Replication monitor I see that the replication agent gets a 10 Minutes no activity seen message. Therefor I started the merge process manually with Outputverboselevel 2. It is hanging again, the outputfile tells me that sp_MSadd_merge_history90 is executed. How to resolve this issue?
On one of our machines, all of the SQL Server 2000components except for the main Server component (SQL Servercore) itself were installed (Management tools, etc) a while agoand everything was running fine. Now I go and add/install theServer component and then Service Pack 3a.It seems that Service Manager won't start up (I get an hourglass cursor)and now I find that Enterprise Manager won't run as well. No errormessages appeared and I don't think I saw anything unusual inthe log file.However, I can use Enterprise Manager on a differentmachine and connect to the database (so the databaseitself seems to be running).Any suggestions as to what the problem might be and how tofix it? I like to see if I can repair this without havingto do a reinstall.Thanks.PF
IF someone can assist me. Everytime I load up enterprise manager the service manager turns off. And the enterprise manager can't connect to the local database. But everytime i turn it back on and try to connect again it shuts it off and around and around we go. Help would be appreciated. Thanks.
We had transactional replication set up by a consultant with remote distributer, push subscription to the publisher (main production database). However, the subscriber machine had fatal crash and is unrecoverable. Now, replication jobs have been failing on distributor and we immediately need to disable and remove replication as it has started causing problems with transaction log backups on production database.
How can I completely remove this whole replication from publisher and distributor?
I have a db (with replication enabled) which was marked as suspect. As per the logs it is the Hardware crash that caused this db to become suspect. Tried with sp_resetstatus to recover the db. But it is still in suspect mode. Changed the db into emercengy mode to recover the data thru' bcp which was succesful. Since there is no other way to recover the db, now I want to drop the db and create / restore the db from backup. I am unable to drop the db becasue it is having a publication. I am also unable to drop publication becasue now the db is in emergency mode. Kindly help and inform how I can drop the db and create it again from the backup without reinstalling SQL Server again.
Does anyone know how to remove 'Replication Triggers'?
I have a database created by export of data object. This process does not export any system tables to do with replication but there still seems to be something in the database which references them. There is no poblem if I backup and restore the dataabse.
Several years ago I set up Merge Replication on a SQL 2000 database and an MSDE Client on a Laptop. The Laptop frequently travelled out of the country and would "synch" up when it came back in.
Well the Laptop received some Viruses that we cannot get to remove so putting it on the network is not possible. Also, the owner of the laptop received a new one. He wants the database set up on the new laptop but it is not a priority at the moment and we plan to wait till the "Yemen" project is finished.
In the mean time, I want to remove the old laptop out of the Merge Replication scenario. We are not concerned about losing the data in the database on the laptop.
Does anyone know the steps I need to perform to "unreplicate" my database without being able to connect them?
SQL Server 2005 Standard replicating to an identical server.
My issue:
When we go into the database to remove a large number of rows, it says we are unable to delete since the database is in replication. Is there a way to pause, or stop replication temporarily? I stopped the log reader but it still gave me the same error.
The only way I have found around this is to delete the publication and re-create it when I'm ready. Now though, I'm unable to delete the publication. SQL Server Management Studio will freeze if I either try to delete something from the UI or command line. This happens with objects in SQL Server as well as rows and such. It will just freeze and I have to kill the process.
I'm trying to write a create database script for a test database and I need to check if the database exists before dropping and recreating it. The problem I'm having is that the test database is also merge replicating so if the db exists I need to remove the replication and then drop the database. I'm running the script using osql from a NAnt build script. The script goes something like this:
USE master GO if exists (select * from sysdatabases where name = N'@INITIAL_CATALOG@') BEGIN USE [N'@INITIAL_CATALOG@'] EXEC sp_dropmergepublication @publication = N'@PUBLICATION@' USE master EXEC sp_replicationdboption @dbname = N'@INITIAL_CATALOG@', @optname = N'merge publish', @value = N'false' DROP DATABASE @INITIAL_CATALOG@ END GO CREATE DATABASE ...
Where the NAnt script replaces the @PARAMETER@ fields before running the script. Running the script using osql when the database doesn't exists appears to fail on parsing the line "USE [N'@INITIAL_CATALOG@']" with the error "Could not locate entry in sysdatabases for database '[DatabaseName]' ..." and does not create the database. If I run the same script in SQL Management Studio I get the same error but it does create the database.
The script should only execute the USE [N'@INITIAL_CATALOG@'] statement if the database exists, but the parser isn't able to see this and returns an error. If anyone can see an error in this script syntax, or see a different way of doing the same function without getting errors I would greatly appreciate it.
I installed SQL Server MSDE 2000 but I can't find how to start it. Does this package include an Enterprise Manager or not? I thought that maybe it was a standard XP Pro feature. I had no problem finding it in W2000 Pro.
Has anyone encountered this error: When you are in Enterprise manager and you select a database then the tables tab and then you select a table and go to open table- select all rows, I get an error--An unexpected error happened during this operation-Query Designer encountered a query error! Please let me know if you have seen this. Also, when I access this from one networked computer I get the same error, then when I access it from another I do not!! The servers are interacting with Pivotal. The one that works does not!!
Hi all, I have SQL 7.0 desktop addition installed on my local win NT workstation. I am able to connect to my local server using Quary Analyser but when i am trying to connect using EM, i am not able to connect. I am receiveing the following error message. __________________________________________________ ___________________________ A conncetion could not be established to "servername" - Specified SQL Server not found. ConnectionOpen(CreateFile()). Please verify SQL server is running and check your SQL Server registration properties(by right clicking "servername" node) and try again. __________________________________________________ ___________________________ I have tried as said in the error message and also tried connecting with "sa" but its not working. I can see that the server is running and i am able to connect through QA.
I am fairly new sql dba in a company and I am sure Enterprise Manager is installed on PC's and it shouldn't. Is there a way of finding out other then visiting each workstation. Thanks in advance..
I am considering upsizing my Access 2000 DB to a SQL 7 server. I was told that having SQL 7 Enterprise Manager is highly prefferd but not essential as I can maintain the upsized DB with Access 2000. The only way that I have been able to find JUST enterprise manager seems to be with purchasing the whole SQL 7 program for $1300! Microsoft cannot be that cruel, that you have to buy the whole program just for Enterprise Manager!
My questions are:
Can I download just MS SQL 7 Enterprise Manager anywhere for a reasonable fee or free?
and
if not, can I continue to use Access 2000 to maintain the SQL 7 upsized DB?
I have access to a SQL 7 server via my ISP Hosting account. I know Enterprise manager comes with the server software, but how can I get a copy of JUST Enterprise Manager?
Is it possible to administer both 6.5 and 7.0 databases from the same SQL Enterprise Manager? I have read that you cannot do this because the 7.0 "plug-in" to the MMC wont work with 6.5 databases.
We had database corruption and cannot access the Enterprise Manager. DBCC returned errors 9000 to 9999 which I can't get any suggestions on how to handle from BOL. Any ideas!!!!! Thanks.
Hi, I would like to know if we can present users to access details database information about the databases on a server through Enterprise Manager. If you create a SQL login and do NOT give it access to any database, if someone logons on your server with enterprise manager, even though he does not have access to any database, he will still see the list of all database on your servers plus tons of sensitive information like database owner. Is is possible to limit enterprise manager to only view information about database that the user has access to?
How can I force users of Ent Manager 6.5 to enter a name/password when connecting to a server that has been registered? I dont want to use the sa name and password so that anyone could use my workstation to access our servers.
Does anyone know how to turn off or disable the auto discovery for Enterprise Manager. Apparently our Network group is complaining that Enterprise Manager is generating noise on the network, it is not signifcant in volume but they complain it impacts there ability to detect hacking attempts on our network because it causes some false positives. I generally keep Enterprise Manager running because I will always have some manual job running from it and we have so many servers it takes awhile for them to all load when I first fire it up.
I have SQL server 2000 client machine on my XP desktop which worked fine until yesterday. Yesterday, I tried to set up client access (a tool from IBM to access AS400) unsuccesfully. Since ever, Each time I try to open a table in enterprise manager, I get the following error message "The query cannot be executed because some files are either missing or not registered. Run setup again to make sure the required files are registered". While when I issue a query in analyzer it works fine.
I did that several times without success. Even, I removed the whole SQL 2000 setup, rebooted my machine, ran set up again for client tools which gave the same result. Also, I re-setup MDAC2.6 SP2 but no way.
Which files are corrupted ?and I don't understand after doing all that, setup goes smoothly without indicating any errors, but still when you open a table in enterprise manager, it gives the same error.
Using MS SQL Server 7. When I go into a table in design view and order by date created, it only orders on the day and not the date (Enterprise Manager) e.g.
When we click on the Query Analyzer Shortcut, it will prompt for a user id and password.but when we expand the databases node from EM and clicks on Tools->Query Analyzer Menu, after selecting a database node, the QA does not prompt for the user id and password. Can any one explain this behaviour of QA..
I am using Mixed mode authentication for my db server.