Recent content by jcrivera

Yes indeed... If you read again (at the end of my post) the three problems I found so far (DMZ, update triggers, sql version) I'm stating that if I remove ANY of these three variables, the UPDATE statment works without any problems. The problem arises when the 3 variables are present at the...

Greetings... I have two SQL 2000 servers, A and B, being Svr A in our local domain, and Svr B is in a DMZ (i.e. in the internet). Svr A can see Svr B, but for security reasons, Svr B cannot see Svr A. This is OK. From Svr A, I'm trying to make a distributed (remote) UPDATE being the source...

This is my scenario... Server A Server B Server C (SQL Svr 7) (SQL Svr 7) (SQL Svr 2000) (NT4 Svr) (NT4 Svr) (W2K Svr) Server A is outside a firewall. Server B and C are inside our company's W2K domain. Server B has Server A and C as linked servers. Server C...

Oops! I'm sorry. Didn't realize that detail.

This is my scenario... Server A Server B Server C (SQL Svr 7) (SQL Svr 7) (SQL Svr 2000) (NT4 Svr) (NT4 Svr) (W2K Svr) Server A is outside a firewall. Server B and C are inside our company's W2K domain. Server B has Server A and C as linked servers. Server C...

Excuse me, let me rephrase my question... When I replicate (transactional, allowing immediate update-subscriptions) what should I do to refresh the publication and subscription after a new column is added to a table, already defined as an article? Hope I'm clear now. J.C.

Greetings. When replicating (in 7.0), after I define a published article (in a table) and configure a suscription to that article, is there a way in which the customized stored procedures could be modified to accept NEW columns that are added into that table? I'm using transactional...

Greetings. According to what is configured on the publications, the system blocks after X minutes (10 by default) of inactivity have passed. This implies that the Agents and Publishers stop, the replication jobs bomb and there's no way to make them to start again. When this type of block...

Terry et al: We were able to recreate this problem and it is in the following way: Let's assume this scenario. Server "Svr-A" is remote, and Server "Svr-B" is local. Both are version 7.0 (1) Logging locally in server A (either by the Query Analyzer or Ent.Manager), go...

In that case, what procedure should I follow? Shall I treat the 2000 svr as an ODBC data source, or as a normal SQL Server? (I mean, when trying to add it as a linked server). Please advise. J.C. PS: I try to add it in either way and, for example, when trying as an ODBC, I get this error...

We're using SP3. Do u think that running this script file (instcat.sql) with SP3 would help? Please advise. J.C. :-)

Greetings Terry. Thanks for your assistance and comments. We already know that if a change in the base table structure is done and the view to that table is not properly refreshed we'll get this type of metadata errors. However, what Ed is trying to explain is different. Our situation...

Yep, I noticed... Nevertheless, what I did was to force the behavior like the one I was expecting by means of a trigger. It's working fine now. Thanks.

My scenario is the following: (SQL Svr 7.0) I have a table that contains (among others) a column "MyColumn" that up to now it has been defined as NULL due to business rules. So, although this column can indeed allow null values, however I would like to create a UNIQUE constraint to...

This is my scenario: I got two SQL Server 7 servers (let's name them A and B). The firewall has been defined so that server A can't see server B (for data security reasons); however, server B can see server A. The replication has been configured in such a way that server A is the publisher...