"Wrap" replication files

Is there a way to distribute merge and transactional replication commands/files such that a slight hiccup in the connection does not cause replication to fail? Maybe like wrapping them in a zip or other type of file?No, nothing built in, but even if that were the case that won't prevent problems, what if the connection failed during the transfer of the zip file? There's built-in retry logic in the agents for network failures, is this not working correctly for you?|||What do you mean by built-in? Is this supposed to be automatic? Are there settings or distributor properties/parameters I have to set for this? I am not talking about a total loss of connection - just a slight hiccup in communications. Maybe the files could be buffered somehow during the transfer. Is there a way for a custom application to interact with this process?|||distribution agent should retry 10 times before completely stopping, you can increase this interval. For merge agent, since it's scheduled it should just pick up again where it left off on the next sync, or if you're using rmo, you can always check for a disconnect and resubmit a sync.

"The underlying connection was closed: An unexpected error occurred on a receive." End

what can cause the above error when connecting to an endpoint via a c# app? the app, and sql are both on my machine ( im just doing this for test purposes and to learn something new.)

i added this code on advice from a web site to the Reference.cs file:

{
HttpWebRequest webRequest = (HttpWebRequest) base.GetWebRequest(uri);

webRequest.KeepAlive = false;
webRequest.ProtocolVersion=HttpVersion.Version10;
return webRequest;
}

Now i get this error.

"The request failed with HTTP status 401: Unauthorized."

this is strange as i have granted the user who the application is running under control access to the endpoint, and even to the function behind the endpoint.

Here is the code behind the button for calling the web service:

private void button1_Click(object sender, EventArgs e)

{

try

{

v_fintag.my_Endpoint wsObject = new v_fintag.my_Endpoint();

wsObject.Credentials = System.Net.CredentialCache.DefaultCredentials;

System.Data.SqlTypes.SqlInt32 sqlint;

sqlint = 25;

System.Data.SqlTypes.SqlString sqlStr;

sqlStr = wsObject.GetFunctionData(sqlint);

}

catch (Exception ET)

{

label2.Text = ET.Message + " : " + ET.Data;

}

}

Also, here is the endpoint, in case its useful or provides information:

create endpoint my_Endpoint

state = started

as http(path='/sql',

authentication=(INTEGRATED),

PORTS=(CLEAR),

SITE='*')

For SOAP

(

webmethod 'GetSprocData'(name='adventureworksdw.dbo.testEndPointSproc'),

webmethod 'GetFunctionData'(name='adventureworksdw.dbo.endpointFunctionTest'),

wsdl=default,

schema=standard,

database ='adventureworksdw',

namespace = 'myNamespace'

)

grant execute on dbo.endpointfunctiontest to [user1]

use master

GRANT CONNECT ON ENDPOINT:: my_Endpoint TO [user1]

"dangerous MSI" Microsoft SQL Server 2000 DTS Designer Components

Microsoft SQL Server 2000 DTS Designer Components has cause a total destruction of my Enterprise Manager.

In my workstation I've got Sql Server 2000 client and Sql Server 2005 client. Everything goes fine up to here.

But when I've installed that MSI I have not been able to open my Enterprise Manager.

From MMC appears: Error initializing component CLSID: {xxx.xxx}

My goal was be able to open 2000 stuff from Sql Management Studio. By the moment, I'm forget of that.

Does anyone have ever faced this issue?

QA is working.

Thanks in advance for any suggestion

is this an issue? I'm not worried about -I have multiple TS-. But I don't know if it's strongly related with my own workstation settings or is some more general.

My idea was to allow anyone use Sql Management Studio for Sql25k stuff and Sql2k stuff to the full (it included dts 2000) and so and cutting out time.

|||hey guys any ideas?|||

I know, such a pain, day in day out but I can't believe that anyone has ever experimented...

|||Install sp4 on the client. That fixed the problem for me.|||SP4 for Sql Server 2000, you mean?|||First, if you had 2000 client tools and 2005 client tools installed you did not need to install the "DTS designer tools". First thing to do is uninstall it. You only need to install that package if you DON'T have 2000 client tools.

Then, figure out why you are getting the error "You need DTS Designer Tools" when you try to open DTS in 2005.

I found I had SQL 7, 2000 and 2005 client tools installed. If I uninstalled the 7 client tools, the DTS started working.

Also, make sure you have SP4 of 2000 installed on your machine.

> different DataSets in one Table

Hi! I'm using RS52005. Is it possible to use table while getting data from 2
different datasets? I need this, 'cause I must put data into RS Table from 2
different Databases (Oracle and MS SQL Server)...
regards,
gNMNo, it is not possible to merge two datasets in a data region /
control.
The workaround for this is to merge them into a single dataset. In the
past, I've created a linked server from SQL Server to an Oracle server
and handle the merging of the data from the 2 sources via sql.
Andy Potter