I run replication among several SQL 6.5 Servers with SP3. Recently,
I've applied SP5a to publisher/distributor. After that, some publications
continued to replicate normally, but two of them started to act strangely -
the distribution tasks end succesfully, but it seems that no transactions
were marked for replication.
After investigating a bit, I've found that the data that continued to
replicate normally is modified by stored procedures, while problematic
tables are updated directly. Then I've tried to run isql/w updates against
problematic tables - all the changes were succesfully applied to the
subscribers. The other difference between problematic and non-problematic
tables is their size - problematic tables are much bigger and more
frequently updated.
All the subscribers are still SQL 6.5 Servers with SP3. One of them
is also a publisher that uses SP5a-upgraded SQL Server as remote
distributor. Its publications replicate OK.
I am trying to apply SQL Server Service Pack 5a to my original SQL Server 6.5 but an error keeps coming up "Setup initialization could not be successfully executed. ISQL,EXE could not be executed.Pls check relevant .out file".
The last line of the relevant .out file produced by this error is:
You cannot run SELECT INTO this database. The DBO would have to run sp_dboption to enable this option.
Msg 208, Level 16, State 1, Server REYWINNT, Procedure sp_helpsort, Line 295
I have a third party app that has been 'certified' by the vendor on SQL 6.5 SP5. We are aware of the dump database issues when using SP5 and Enterprise Manager. We would like to use SP5a to get around those issues.
Is anyone aware of any other 'bugs' or problems that have come about in SP5a....
I've got a script that runs regularly to monitor log space usage on a SQL 6.5 sp5a server. Where the log space usage is greater than 75% it then dumps the log. However the Enterprise Manager screen still shows usage as being above 75%. I'm aware that I need to run dbcc checktable(syslogs) to have EM reflect the change, and my question is: Within my sql script how do I switch context to the database where I need to run the dbcc checktable(syslogs) command?
I've installed SQL Server Service pack 5a on our test lab Database and have come up with problems with my protocol. Everything works fine IF I set the Net Library to Named pipes. But before the service patch, I was running Multi-Protocol WITH TCP/IP (much faster). How can I make SQL use Multi? Using Named pipes screws up my replication. Any suggestions???
While installing the service pack 5a, I had the following error "setup could not be successfully completed, ISQL.EXE could not be executed. Please check the relevant *.Out file.
Now I am unable to start up my SQL service. When I try to start it , I get the following message: Error : 1105, Severity: 17, State: 2 Can't allocate space for object 'Syslogs' in database 'master' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.
Apparently 4 mb of free space in my master database was not enough for the service pack. I can't extend the size of my Master database because I can't get the SQL service to start.
I am having problems with stack dumps (as many as 12 a day) at a production site running NT 4.0 SP4 with Sql Server 6.5 SP5A. I've tried running every diagnostic utility on the server but it shows no problems. Before I open a ticket with Microsoft on the stack dumps, I'd like to upgrade the server to NT Service Pack 6A. My question is, do I need to re-install SqlServer SP5A? Will the NT Service Pack 6A invalidate SQL SP5A?
Hi all, I recently upgraded to SQL 6.5- sp5a. I run DBCC TEXTALL as part of my nightly maintenance. Our db is about 3 GB and is heavy on text fields. Since the upgrade, DBCC TEXTALL hangs up the server until I reboot it. The last message in the error log is "Warning: out of RA slots... comfigure more RA slots." (or something like that). This never happened before. BOL says don't monkey with the RA slots per thread, so I've been adjusting the number of RA worker threads. I raise it, bounce SQL SERVER, and try to run the DBCC TEXTALL again. Same results. Eventually I got up to 10 RA worker threads, at which point I got an "IO buf_wait" error, which also hung up the server. I've read that increasing RA worker threads will eventually run you out of buffer space, and it looks like that's what happened.
I'm beginning to think that the problem isn't really with isn't really with the number of RA worker threads I have configured, but rather with something that sp5a changed. Or maybe DBCC TEXTALL is running into some sort of corruption it can't handle... Or something... So, I'm reading up on the relationship between buffer cache, RA, etc., but the sad fact is that information on that low down level is hard to find, and I don't understand most of it anyway. Any suggestions, reading recommendations, comments, or jeers would be highly appreciated.
we have a client that just upgraded to sp5a and are encountering problems...one stored procedure seems to routinely become corrupted, and does not complete correctly. however, it does not error out, and the only way to tell that it did not complete successfully it to query the data.
the only solution that i have found to this problem is to recreate the procedure. i have tried using sp_recompile to force a recompile at next runtime, and the problem still occurs. i have tried recreating the calling procedure, and recreating procedures it calls, but neither fix the problem. after recreating the procedure, it continues to run fine for anywhere from 1 hour to 8 hours, and then starts to fail again.
microsoft so far has not been able to give us help in diagnosing this, and i am coming up with nothing in my own investigations.
has anyone seen a problem like this in sp5a?
also, it is occurring on 5 similar dbs that are on the same server...
When running Enterprise Manager from my desktop pc to try and expand a database device I am unable to do so. The size shown is negative, and the max size is the same, with the 'Change Now' box greyed out. When I log on directly onto the server I can easily expand the db device. There is lots of free space on the server. Our set up is quite small with four NT workstations and two NT servers with SQL Server 6.5 on them. All these six machines are in the same workgroup. The workstations are on a separate floor to the servers, which are in the computer room. I have a feeling this is a networking issue. Can anyone suggest why this is happening?
After applying SP 5a I found out that my SQL strings with sums and groups produced double rows. I found out that grouping one column (type CHAR(6)) produced two distinct rows of the equal values.
All the values in that column have 4 characters, but it seemed like some distinct values were grouped by the whole field length i.e 6 characters. I haven't seen earlier that those blanks after field value change the grouping results.
When I transferred the table and data to old SQL Server without any SPs, query showed distinct values correctly.
The sort order and other settings are the same. Can anyone tell where to look for help?
Hi I've recently upgraded 4 sql servers to sp5a and have just found that BCP fails on all of them with a DR Watson error. I did reinstall the Nt sp after installing sql server sp5a. Can anyone help ? Thanks
Has anyone gotten clustering to work via the Cluster Wizard in SP5a?
I've got two ProLiant 5500's with the Compaq Clustering S/100 option. I've done a fresh install of NT Enterprise 4.0 SP3, then installed clustering with the Compaq S/100 drivers... everything fails over nicely, can make shares off the virtual server, etc. I then install SQL Server 6.5 EE, then apply SP5a -- so far, so good.
Now I try to run the clustering wizard. The wiz prompts me for my SA password. I enter it, and it gives me a message box that it can't start or log onto the database... but when I look in the event log it appears to have logged on successfully with a Non-trusted connection.
Hello, Just in case anybody has had this problem after applying service pack 5a. a stored procedure that sets serial numbers on records on a temporary table is skipping every other record. I ran the code manually on isql and could not replicate the error, however when re-compiled on stored procedure it fails misserably. when is Microsoft going to release a service pack that actually works?
Did you know that Executive does not recognize 2000 as a leap year?
If anybody has any suggestions on this problem, besides the obvious (using a real table) please write back thanks.
I'm getting this, after upgrading from 2000 to 2005.Replication-Replication Distribution Subsystem: agent (null) failed.The subscription to publication '(null)' has expired or does notexist.The only suggestions I've seen are to dump all subscriptions. Sincewe have several dozen publications to several servers, is there adecent way to script it all out, if that's the only suggestion?Thanks in advance.
Hi,I have transactional replication set up on on of our MS SQL 2000 (SP4)Std Edition database serverBecause of an unfortunate scenario, I had to restore one of thepublication databases. I scripted the replication module and droppedthe publication first. Then did a full restore.When I try to set up the replication thru the script, it created thepublication with the following error messageServer: Msg 2714, Level 16, State 5, Procedure SYNC_FCR ToGPRPTS_GL00100, Line 1There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in thedatabase.It seems the previous replication has set up these system viewsSYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replicationmodule again to see if it drops the views but it didn't.The replication fails with some wired error & complains about thisviews when I try to run the synch..I even tried running the sp_removedbreplication to drop thereplication module, but the views do not seem to disappear.My question is how do I remove these system views or how do I make thereplication work without using these views or create new views.. Whyis this creating those system views in the first place?I would appreciate if anyone can help me fix this issue. Please feelfree to let me know if any additional information or scripts needed.Thanks in advance..Regards,Aravin Rajendra.
In my production box is running on SQL7.0 with Merge replication and i want add one more table and i want add one more column existing replication table. Any body guide me how to add .This is very urgent Regards Don
DBCC OPENTRAN shows "REPLICATION" on a server that is not configured for replication. The transaction log is almost as large as the database (40GB) with a Simple recovery model. I would like to find out how the log can be truncated in such a situation.
Hello,I'm getting the following error message when I try add a row using aStored Procedure."The identity range managed by replication is full and must be updatedby a replication agent".I read up on the subject and have tried the following solutionsaccording to MSDN without any luck.(http://support.Microsoft.com/kb/304706 )sp_adjustpublisheridentityrange (http://msdn2.microsoft.com/en-us/library/aa239401(SQL.80).aspx ) has no effectFor Testing:I've reloaded everything from scratch, created the pulications from byrunning the sql scripts generated,created replication snapshots andstarted the agents.I've checked the current Identity values in the Agent Table:DBCC CHECKIDENT ('Agent', NORESEED)Checking identity information: current identity value '18606', currentcolumn value '18606'.I check the Table to make sure there will be no conflicts with theprimary key:SELECT AgentID FROM Agent ORDER BY AgentID DESC18603 is the largest AgentID in the table.Using the Table Article Properties in the Publications PropertiesDialog, I can see values of:Range Size at Publisher: 100,000Range Size at Subscribers: 100New range @ percentage: 80In my mind this means that the Publisher will assign a new range whenthe Current Indentity value goes over 80,000?The Identity range for this table cannot be exhausted! I'm not surewhat to try next.Please! any insight will be of great help!Regards,Bm
I have a VB.net app that access a SQL Express database. I have transactional repliaction set up on a SQL 2000 database (the publisher) and a pull subscription from the VB.net app. I use RMO in the VB app to connect to the publisher. My problem is I am getting some strange behaviour as follows
- if I run the app and invoke the pull subscription it works fine. If I then close my app and go back in, I can access my data without any problem
- If I run the app and try to access data in my SQL Express database it works fine. I can then close the app, reopen it and run the pull subscription it works fine
however.......
- if I run the app, invoke the pull subscription (which runs fine), and then try to access data in my local SQL Express database without firstly closing and reopening the app, I get a login error
- if I run the app, try to access data in my local SQL Express database (which works fine), and then try to run the pull subscription I get a "the process cannot acces the file as it is being used by another process" error. In this case I need to restart the SQL Express service to be able to run replication again.
I get exactly the same behaviour when I use the Windows Sync tool (with my app open at the same time) instead of my RMO code to replicate the data.
I am using standard ADO.Net 2 code to access my SQL Express data in the app and closing all connections etc
I have recently setup a transactional replication in MS SQL 2000. After setting up the replication the clients TempDB grew by almost 60GB. Now the client is Blaming me for the TempDB GROWTH and saying that its because of the replication being setup i tried to convince them but they are not satisfied yet. Can anybody please tell me does replication cause the tempdb to grow. If yes then how. can u suggest any good link for getting to know the internal working of SQL Server replication????
I know that adding a column using ALTER TABLE to add a column automatically allows SQLSERVER 2005 to replicate the schema changes to the subscribers, however, I would like to add a new column to an existing article that is being used for merge replication, however, I don't want this column to be replicated. Re-initialising the subscriptions is not a option. Help would be appreciated.
I have been researching on the proper steps or sequence to follow to completely remove SQL Server 2012 Transactional Replication. I have read articles about using SSMS as well as using replication stored procedures and some procedures use SQLCMD or just regular TSQL executed in SSMS. I have also read articles where people said all you really need is connect to the Publisher instance, find the publication you want to remove and choose "Delete" and everything will be taken care of behind the scene. I have three SQL servers that participate in transactional replication. SQL-P (publisher),
SQL-D (distributor) and SQL-S (subscriber). Do I need to connect to the distributor instance and the subscriber instance when removing transactional replication or is it just really connecting to the publisher and click delete on the publication? I want everything gone including any metadata, systems tables, distributions db and any other replication objects created during the initial configuration.
Hello everyone,I am involved in a scenario where there is a huge (SQL Server 2005)production database containing tables that are updated multiple timesper second. End-user reports need to be generated against the data inthis database, and so the powers-that-be came to the conclusion that areporting database is necessary in order to offload report processingfrom production; of course, this means that data will have to bereplicated to the reporting database. However, we do not need all ofthe data in the production database, and perhaps a filtering criteriacan be established where only certain rows are replicated over to thereporting database as they're inserted (and possibly updated/deleted).The current though process is that the programmers designing thequeries/reports will know exactly what data they need from productionand be able to modify the replication criteria as needed. For example,programmer A might write a report where the data he needs can beexpressed in a simple replication criteria for table T where column X= "WOOD" and column Y = "MAHOGANY". Programmer B might come along amonth later and write a report whose relies on the same table T wherecolumn X = "METAL" and column Z in (12, 24, 36). Programmer B willhave to modify Programmer A's replication criteria in such a way as toaccomodate both reports, in this case something like "Copy rows fromtable T where (col X = "WOOD" and col Y = "MAHOGANY") or (col X ="METAL" and col Z in (12, 24, 36))". The example I gave is reallytrivial of course but is sufficient to give you an idea of what thecurrent thought-process is.I assume that this is a requirement that many of you may haveencountered in the past and I am wondering what solutions you wereable to come up with. Personally, I believe that the above method isprone to error (in this case the use of triggers to specifyreplication criteria) and I'd much rather use replication services tocopy tables in their entirety. However, this does not seem to be anoption in my case due to the sheer size of certain tables. Is thereanything out there that performs replication based on complexprogrammer defined criteria? Are triggers a viable alternative? Anyalternative out-of-the-box solutions?Any feedback would be appreciated.Regards!Anthony
I am working on bringing our disaster recovery site to be a live site. Currently we replicate to one of out servers (server B) with merge replication (from server A). Server A also does one way transactional replication form some table to several other servers including servers at the DR site.
This setup is not going to be fast enough for what we need so I am wondering if a table is receiving merge replication will the merge updates also replicate down the transaction path??
Example... Server B update a row and merges to Server A. With this update them replicate (via transactional) to Server C??
I have a wired situation..!I set up transactional replication on one of my development server (SQL2000 Dev Edition with sp4).It is running fine without any issues and all of a sudden, i noticed inmy repication monitor tab under Publisher where I usually see thepublication is empty now.I do see the snapshot agent, log reader and distribution agent under myagents inside the replication Monitor. But its usefull to see all 3agents in one window under publisher before. What happend? Is there anyway to get that inside that monitor? Has someone encountered thissitation before? Please advise....After that I tried to create a new set of replication on differentdatabase on the same server and i dont see those either underReplication Monitor - Publishers....All it says is (No Items)....I would appreciate any help to correct this issue... Thanks in advance..
I have setup transactional replication everything on one box. later(two or three weeks later), Replication monitor is show red X Under my publishers (publications is disconnected). this is SQL2005.
