Viewing 15 posts - 151 through 165 (of 253 total)
something like this?
DECLARE @t table (primarykey int, acctid int, statusid int)
insert into @t values (1, 2, 1)
insert into @t values (2, 2, 1)
insert into @t values (3,2, 2)
insert into @t...
July 5, 2006 at 5:35 pm
BCP is faster than DTS.
July 5, 2006 at 11:18 am
http://www.replicationanswers.com is a good wesbsite from Paul Ibison.
There are a lot of commonly observed error messages and a possible fix.
June 27, 2006 at 4:26 pm
you didnt answer my questions.
you can generate those stored procs using sp_scriptpublicationcustomprocs @publicationname. This will generate the insert/update/delete stored procs for all articles in the publication. You could use only...
June 27, 2006 at 12:28 pm
What is the structure of the table? And how many records do you have in the table? And is this the first time you set up replication or it was...
June 27, 2006 at 9:55 am
Thanks John.
I was finally able to get it set up and running. I am gonna make a document and put it on my blog somewhere one of these days. I...
June 27, 2006 at 9:53 am
If your row size is big, perhaps you might want to use TEXT data type. But there are some pay offs for using TEXT data type. Check out docs and...
June 26, 2006 at 5:48 pm
There are a lot of things here.
Whether the Groups table has data or not does not matter here since GroupId seems to be coming from the parameter list in your...
June 26, 2006 at 4:56 pm
SELECT Users.userId, userName, userPassword, Users.branchId, UserGroups.groupId
FROM Users JOIN UserGroups
ON Users.branchId=UserGroups.branchId
AND Users.UserId = UserGroups.UserID
June 26, 2006 at 4:50 pm
I think once the subscription expires you need to resetup replication from scratch.
June 26, 2006 at 12:05 pm
we are changing the datatypes of columns from int to bigint etc. so repladd/repldrop will not work.
thanks
Dinakar
June 26, 2006 at 12:02 pm
AFAIK, you need to drop all foreign keys on subscriber.
June 26, 2006 at 11:49 am
You could do a count(*), min(date), val and group by val.
June 23, 2006 at 3:19 pm
If you already have the error, the only solution I would think is to re-setup replication but make sure you check the "never expires" option as Borik mentioned. By default...
June 23, 2006 at 3:08 pm
Viewing 15 posts - 151 through 165 (of 253 total)