Hi All,
Can anyone explain me, why we have Resource and Distribution System
Database in SQL Server 2005. Whether they were also available in
previous versions also.
Thanks in Advance.
Regards,
Om
I have a 2005 server that is upgraded to SP2 and the error log indicates it is version 9.00.3042.00. However, the system resource database for the same server is reporting as version 9.00.2047.00. From another post I have found out the some replication problems I am having are due to this discrepancy.
I have reapplied SP2 hoping it would change the resource db version, but it did not. Is there another way I can upgrade the resource db without re-installing SQL from scratch?
Thanks!
I just finished installing SQL Server 2012 with the SQL Server Replication feature component checked. On configuring transaction replication, i notice the distribution database wasn't there. I ran the below query
EXEC sp_get_distributor And the value for distribution_db_installed is 0 as shown below
installed distribution server distribution db installed is distribution publisher has remote distribution publisher
0NULL000
Hi, I am using OPENROWSET command to read from a dbf file in Transact-SQL of SQL Server 2005. Query runs fine for a few tries after that i get the error:
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Microsoft][ODBC Text Driver] System resource exceeded.]
If a restart the Server everything works fine, but then the problem starts again. I saw a related postinf with no
acceptable answer, unfortunately.
Thanks in advance,
--Dimitris Doukas
I have a page that was working but now I am getting the following errors.
Server Error in '/' Application.
ERROR [HY001] [Microsoft][ODBC Text Driver] System resource exceeded.ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failedERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [HY001] [Microsoft][ODBC Text Driver] System resource exceeded.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.Odbc.OdbcException: ERROR [HY001] [Microsoft][ODBC Text Driver] System resource exceeded.ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failedERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended PropertiesERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDRERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMTERROR [HY001] [Microsoft][ODBC Text Driver] System resource exceeded.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[OdbcException (0x80131937): ERROR [HY001] [Microsoft][ODBC Text Driver] System resource exceeded.
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute Extended Properties
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute HDR
ERROR [01S00] [Microsoft][ODBC Text Driver]Invalid connection string attribute FMT
ERROR [HY001] [Microsoft][ODBC Text Driver] System resource exceeded.]
System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) +35
System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle) +131
System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) +98
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.Odbc.OdbcConnection.Open() +37
DevSite_ImportStep1.btnUpload_Click(Object sender, EventArgs e) +219
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +105
System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +107
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102
I am uploading a text file to a MS SQL 2000 database using an ODBC driver. Here is the code:
<code>
FileUpload1.SaveAs(fpath + "" + fn)
litStep1.Visible = TrueDim FieldCount As Int16
Dim FileType As Int16Dim cmd As SqlCommand
Dim dr As SqlDataReaderDim conn2 As OdbcConnection
Dim dr2 As OdbcDataReader
Dim cmd2 As OdbcCommand
conn2 = New OdbcConnection("Driver={Microsoft Text Driver (*.txt; *.csv)};Dbq=" + fpath + ";Extended Properties='text;HDR=YES;FMT=Delimited'")
conn2.ConnectionTimeout = 200
cmd2 = New OdbcCommand("Select top 5 * from [" + fn + "] ", conn2)
cmd2.CommandType = CommandType.Text
cmd2.CommandTimeout = 300
conn2.Open()
dr2 = cmd2.ExecuteReader()
FieldCount = dr2.FieldCount
conn2.Close()
</code>
Before when this happened a reboot of the sql server resolved the problem. That's not working this time and it's certainly not a practical solution.
Any suggestions?
My Integrity job started failing recently with the following error. Msg 701, Level 17, State 123, Line 1 There is insufficient system memory in resource pool 'default' to run this query. Process Exit Code 1. The step failed.
select @@ version
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4033.0 (X64)
Jul 9 2014 16:04:25
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
System is having 4GB RAM and SQL is using most of it. It has 2 processors.
I am using SQL 2000 (Standard Edition, SP4) and have created a linked server to access a Access MDB file. When I run a simple query against that server, I get the error:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: System resource exceeded.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' ICommandText::Execute returned 0x80004005: ].
I am able to connect to this same Access MDB file from another SQL server (SQL 2000 Enterprise Edition, SP4). I have compared the two servers and they both have the same version of MDAC (2.8) and the same version of the Jet OLE DB Provider.
Any idea why this would work from one server and not from the other. Also, I was able to perform the same queries from the first server a week back.
Thanks in advance for you help.
Amir
Hi all,
I have a 400MB Excel file that I consume from another automated process (don't ask). I copy this file down locally to my server, and I am attempting to create an SSIS package that points to this file via a connection manager. My computer starts gobbling up massive amounts of memory (devenv.exe gets up to about 800MB or so, then drops back down to 100MB) even when I attempt to rename the connection in the connection managers tab.
I have set all BypassPrepare to TRUE and ValidateExternalMetadata properties to FALSE, and still it can take up to 3 to 6 minutes for BI Dev Studio to respond. My specs:
Intel Centrino Duo 2.00 GHz
2GB RAM
XP Pro SP2
There MUST be a way for me to work effectively on a file of this size. Please help! Thanks much for any assistance.
Sincerely,
Brian Pulliam
odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC Microsoft Access Driver] System resource exceeded., SQL state S1001 in SQLConnect
we got the error with access 2000 database and PHP as prog. language .
we created dsn for the connection.
reboot solves the problem. but we need another solution better than this.
after moving the resource database files with this command:
Code Snippet
ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME=data, FILENAME= 'new_path_of_mastermssqlsystemresource.mdf');
GO
ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME=log, FILENAME= 'new_path_of_mastermssqlsystemresource.ldf');
GO
I am getting this error trying to do anything in the instance while I have it started in minimal mode (/f /t3608)
(the instance WILL NOT COME UP UNLESS I USE THE /F /T3608 from a command promt.. please .. any suggestions??????????????????????
File activation failure. The physical file name "E:MSSQLKOCSQLDEV01Datafilesmssqlsystemresource.ldf" may be incorrect.
The log cannot be rebuilt when the primary file is read-only.
File activation failure. The physical file name "E:MSSQLKOCSQLDEV01Datafilesmssqlsystemresource.ldf" may be incorrect.
The log cannot be rebuilt when the primary file is read-only.
Msg 945, Level 14, State 2, Line 1
Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
Hi,
I am going through the BOL for Sql Server 2005 and i came across the topic of RESOURCE DATABASE.
But when i checked in the system databases in the object explorer there was no resource database can anybody tell me where can i find the resource database
Is it possible to deploy SQL Server CE "baked into" a DLL? For example, instead of setting the build option to "Content", can I set it to "Embedded Resource"?
On SQL Server 2005 SP2 for Publisher and Distributor on the same instance, my old snapshots are not being cleaned up.
The following error is in the agent history:
Executed as user: DomainMyUser. Could not remove directory '\vmsql01ReplDatauncPublication_TRANSACTIONAL20070702104416'. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. [SQLSTATE 42000] (Error 20015). The step failed.
xp_cmdshell is enabled and I can run commands like :
exec master.dbo.xp_cmdshell ' md c:TestFolder'
The permissions to the snapshot share and file system are that DomainMyUser has full control.
I have logged into the machine as this user and can remove snapshots so it does not seem to be a permission issue.
On other machines I do not get any errors but the snapshot folder still is not cleaned up.
Any suggestion as to what the problem could be?
Thanks,
Amy
Copy mssqlsystemresource.mdf of a recently upgraded server and paste to an old server have same effect of upgrading via .exe installation?
My idea is to save time and administrative efforts in upgrades (Service Packs and/or Cumulative Updates) using this method.
According to BOL:
The Resource database makes upgrading to a new version of SQL Server an easier and faster procedure. In earlier versions of SQL Server, upgrading required dropping and creating system objects. Because the Resource database file contains all system objects, an upgrade is now accomplished simply by copying the single Resource database file to the local server.
Hi,
I'm new to working with replication & I'm just starting to test some implementations. We're still using the beta, v7.00.517. and... basically nothing works, I can't even open any of the replication management features in Enterprise Manager. As soon as I select any item from the replication menu I get:
Error 208: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'msdb.dbo.MSdistributiondbs'
It's either:
A: a bug, B: something screwed up in my system databases, or C: I'm missing something really obvious.
Any insight would be much appreciated.
Gordo
i would like to drop a distribution database after disabling both susbscriber and publisher .but i get a message saying distribution database is still in use .and as far as i can tell its there is no one using it .also stopped sql agent but no luck . and when i do select @@ servername i get servername is null how do i correct it .
thanks
When setting up Replication in v. 6.5, a 'distribution' database is created, containing these tables:
MSjobs
MSjob_commands
MSjob_subscriptions
MSsubscriber_info
MSsubscriber_jobs
MSsubscriber_status
However, they cannot be accessed via the SQL Server Enterprise Manager interface like tables in other databases, at least I can't get to them. Is this a problem or a feature? I can query them to get their contents, but I'm wondering if there might be something wrong with my installation of SQL Server.
Any knowledge shared would be greatly appreciated.
Regards,
Karl Simanonok
I can't use the distribution database because it doesn't exist, and I can't create the distribution database because it already exists.
A failed replication set up had left a fat distribution database that caused the server CPU to peg 100% when I tried to set up a new Transactional replication (halfway through the wizard).
I removed all replication objects from SMSS, but the only thing that fixed it was deleting the distribution database with an ALTER to OFFLINE and a DROP, and restarting SQL.
Now, I'm unable to set up replication.
When I try, I get the error "Database 'distribution' does not exist. Make sure that the name is entered correctly."
In Distributor Properties, the Publisher is shown with a distribution database of 'distribution'. If I untick that, SQL asks if I want to disable the Publisher. I say yes & get the error "Database 'distribution' does not exist.'
Ok, so let's create it. In the General tab of that window I create a new Distribution database and call it 'distribution'. Then I get the error 'Could not add the distribution database 'distribution'. This distribution database already exists.
exec sp_helpdistributor shows distribution database as 'distribution'
SMSS doesn't show the distribution database at all.
How I can proceed?
We have a production SQL2K DB with publication.
I found replication stopped, distribution database was marked suspect
and log file is gowning.
I have tried using sp_resetstatus and restart server but recovery
said some IO errors reading distribution's datafile, so I guessed distribution database was totally dead.
I have handful documents telling me how to remove replication and
I am going to take that ride.
Before I do anything real,
is there any warning from you Prof people?
is there any trap I may encounter into?
is that OK to rebuild replication after I remove the dead replication?
highly appreciate for any help and comments.
thanks in advance!
-DW-
What job cleans out the distribution database?
Cna you perform maintenance to keep the size down?
Thanks,
Thomas
ThomBeaux
Hello,
I have my distribution database at C drive, I have to move this database to another drive D.
May anybody tell me how do this secure, please.
This production environment so I can't make any mistakes.
--
Regards
Hi all,Is it possible to move the distribution database to a new folder/drivewithout removing replication? I am attempting to do it the same way youwould move tempdb:ALTER DATABASE distribution MODIFY FILE(name = distmodel, filename = 'C:DISTMOVEDdistribution.MDF')ALTER DATABASE distribution MODIFY FILE(name = distmodel_log, filename = 'C:DISTMOVEDdistribution.LDF')But I get -Server: Msg 5037, Level 16, State 1, Line 1MODIFY FILE failed. Do not specify physical name.Thanks,Josh
View 2 Replies View RelatedI would like to use SQL Server Express with Advanced Services for both a centralized publication/distribution database and a local subscribing database for offline.
I need to configure the distribution database but do not see the "configure publishing and distribution" option while right-clicking on the Replication folder in SQL Server Management Studio Express.
How do I get that wizard to show? I do see the "New" -> "Subscription" wizard.
I am fairly new, any help would be greatly appreciated with configuring my centralized database. Thanks in advance!
Hi all,
I have set up sql 2005 transactional replication .The environment here cannot accept latency so I guess I will have to go with sync db option at the distribution db.My question is what should be my distribution db back up strategy.Should it be scheduled after the backup of the publication db.I am confused.Somebody please help me regarding scheduling it.
Thanks,
SATYA
Hi:
I'm an asp.net programmer and my database is in access format.My server is Windows Server 2003 Enterprise Edition Service Pack 1.I do not need microsoft access installed on my server to access my database through asp.net.
I want migrate my database to sql server 2005
Could I access my database in sql server 2005 format (mdf) through asp.net without sql server 2005 installed on the server?
could I buy to microsoft only "Database Engine"? orIs there a free distribution of "Database Engine"?
Thanks!!
Hi there,
I'm a newbie. I've installed a replication between 2 NT4 servers, with SQL 6.5. My logreader tasks has crashed "Can't allocate space for objects 'syslogs' in database 'distribution' etc...". With a DBCC SQLPERF(LOGSPACE) I can see that the log is 100% full, but I can't dump it : when I use DUMP TRAN DISTRIBUTION WITH NO_LOG, my distribution log is still 100% full. So how can I do to dump it and what can I do to prevent it from filling up ? Do I need to dump it like I do for my database but how could it work if a DUMP TRAN doesn't work ?
Thanks in advance.
Sorry for the English, it's not my native language.
I have a distribution database that has grown over 50g. Distribution cleanup takes over 15 hours to run and there are always very few rows in msrepl_Commands. Usually only a few hundred. Everything is being replicated fine, but I fear a storm coming. why distribution would be so large with so few rows? Also, Ghost Cleanup has been running all week, so I'm thinking maybe the records marked for deletion aren't being deleted?
View 1 Replies View RelatedHello,
We are setting up Merge replication and size of the database is
85 GB. How much disk size is feasible to keep for distribution Database.
Is there any % basis (SIZE) for Distribution DB according to the size of the database?
Is it feasible to keep seperate server for Distribution Server or keeping
Publisher and distributor on same same.
Can any one help me!
Thanks!
Is it possible to move a distribution database to another drive without removing replication? I have done some research but I getting mixed answers from Google searches.
Thanks in advance
Dave
SQL Server 2000 | Transactional Replication
Suspected Problem: Distribution Database Transaction Log Not Checkpointing
I have a distributor with a distribution database that keeps growing and growing (About 40 GB in 7 days). The database is using the SIMPLE recovery model but the log continues to accumulate data. I have spent time looking at articles such as: "Factors that keep log records alive" (http://msdn2.microsoft.com/en-us/library/ms345414.aspx) and the one thing that stands out is the Checkpoint. I noticed that I can run a manual checkpoint and clear the log. If the log records were still active, the checkpoint would not allow the log to be truncated. This leads me to believe that the server is not properly initiating checkpoints in the Distribution database even though Recovery Model = SIMPLE and the server Recovery Interval = 0.
I found this: "FIX: Automatic checkpoints on some SQL Server 2000 databases do not run as expected" (http://support.microsoft.com/kb/909369/en-us) but I suspect this is a followup to a problem that may have been introduced with SP4 (since SP4 is a requirement for the hotfix). I am running SP3a (Microsoft SQL Server 2000 - 8.00.850) so I don't think that is the issue. I have several other nearly identical servers with the same version and configuration that have properly maintained log files.
SP4 is not a good option for me at this point - the next upgrade will be to SQL 2K5.
Any thoughts?
Jeff
Is there a way to move the Distribution database (that is currently on the publisher server) to a different server without having to reync the subscriptions.
View 0 Replies View RelatedRyan J. Boyle writes "I'm trying to set up repliction on my SQL 2005 instance. When I run through the "Configure Distribution Wizard" the wizard errors out, here is the following error message that I'm reciving. I can not find any information based on that SQL Server Error number (there is none in the help file go figure)
ERROR MESSAGE:
SQL Server could not configure <servername> as a Distributor
Additional Information:
An exception occurred while executing a Transact-SQL statement or batch Microsoft.SqlServer.ConnectionInfo
Only replication jobs or job schedules can be added, modiifed, dropped or viewed through replication stored procedures. Changed database context to 'master'(Microsoft SQL Server Error 22538)
Any help in troubleshooting what this issue could be that would be great.
Thanks in advance.
Ryan J. Boyle"
I restored a backup of a replication database named "distribution" to a non-replicated development instance (ss2000). Well, when I try to drop the database I am told I can not because it is used for replication. It isn't. But you now how Microsoft is . . . . So the question is: how do I drop the database without rebuilding the server, or jumping through firery hoops????
Thanks!
Scorched