Modifing values from one database to another

I have several databases in a merge replication.
there are two servers linked so i can send data from one to the other. I
mean Server Fenix is linked to Neptune. Neptune is replicating an Feniz is
the Replicator.
When one table in one of the remote computers is changed the trigger make
price =0. This trigger is NOT FOR REPLICATION, because it was causing to many
conflicts before, because it also executed a Store Procedure that change the
Price to some value.
My problem is that I have a store procedure that once this price=0 it has to
delete some data in one databes of NEPTUNE that is not being replicated.
The problem is that I get an error message saying:
SERVER NEPTUNE IS NOT CONFIGURED FOR DATA_ACCESS
So I try to link Neptun to one of those remote machines, but it is not
posible because they are replicating, I guess...
The way I try to reach Neptune si:
DELETE [NEPTUNE].LABORATORIO.DBO.TABLAPUNTOSCOMPRA
WHERE...
I do not know if this is too confusing...
Thanks a lot if some one can help me,
Lina
try this. sp_serveroption 'Neptune', 'data access',true
or
sp_serveroption 'Neptune', 'data access','true'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
news:81870ED4-8413-46A0-A522-9E43B586F41C@.microsoft.com...
>I have several databases in a merge replication.
> there are two servers linked so i can send data from one to the other. I
> mean Server Fenix is linked to Neptune. Neptune is replicating an Feniz is
> the Replicator.
> When one table in one of the remote computers is changed the trigger make
> price =0. This trigger is NOT FOR REPLICATION, because it was causing to
> many
> conflicts before, because it also executed a Store Procedure that change
> the
> Price to some value.
> My problem is that I have a store procedure that once this price=0 it has
> to
> delete some data in one databes of NEPTUNE that is not being replicated.
> The problem is that I get an error message saying:
> SERVER NEPTUNE IS NOT CONFIGURED FOR DATA_ACCESS
> So I try to link Neptun to one of those remote machines, but it is not
> posible because they are replicating, I guess...
> The way I try to reach Neptune si:
> DELETE [NEPTUNE].LABORATORIO.DBO.TABLAPUNTOSCOMPRA
> WHERE...
> I do not know if this is too confusing...
> Thanks a lot if some one can help me,
> Lina
|||Thank you, Hilary.
I have this two sentences inside the store procedure and they do no work.
exec sp_serveroption 'NEPTUNO','data access','true'
EXEC sp_serveroption 'NEPTUNO', 'collation compatible', 'true'
"Hilary Cotter" wrote:

> try this. sp_serveroption 'Neptune', 'data access',true
> or
> sp_serveroption 'Neptune', 'data access','true'
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
> news:81870ED4-8413-46A0-A522-9E43B586F41C@.microsoft.com...
>
>

mobsync.exe errors after installing sql server sp3a

Server : w2k server sp4
Tablet : w2k sp4
Sql Server 2000

A few days ago we upgraded our servers and tablet pc's with sql server sp3a. At the same time we also changed the publisher and it now uses a static filter to reduce the number of records in the tablet database. Since we have done this we have been getting an error message when we try to synchronize via the windows synchronization manager on our tablet pc's. The error message is "mobsync.exe has generated errors and will be closed by windows. You will need to restart the program. I looked up the error message and it is a stack overflow. This does not happen every time but about 50% of the time. We can always sync from within enterprise manager and everything works fine every time.

If any one has any ideas I would greatly appreciate it and thank you in advance.Check thru event viewer for further information and see any other applications are affected such as IE.


What was the previous version of service pack on SQL?|||Satya I checked the application and system logs and there doesn't seem to be anything in them around the times of the failures. However I did find a DrWatson log and after reviewing it I noticed that the problem was there before we installed sp3a. We upgraded from sp2. I noticed that this problem started happening when I changed the publication to use a static filter. We set up the filter on one table on a few fields in the table and this is applied to foreign keys in other tables. The filter is on a job table and we filter on iProcessedFlag < 2 AND sdtDateIn >= '1/1/2003' AND sdtDateFinished IS NULL AND iJobNumber > 5999. The processedflag and the sdtDateFinished signify whether the job is finished or not. This filter is then applied to other tables in the database based on foreign key job_id. There about 8 foreign key linked tables. If you have any ideas why this filter is causing problems point me in the correct direction. This is the same filter that we use on our PDA publication and it works fine although it goes through a different replication mechanism.|||Just wanted to let everyone know the findings on this problem. I had to contact Microsoft after I discovered that it was not sp3 that was causing the problem but was actually the filter that I started using on the publication. There was nothing wrong with the filter, it was a Microsoft problem dealing with the filter. They send me a hot fix to put on each of the units that was experiencing the problem but only time will tell if the problem is fixed. This problem does not happen when you sync from Enterprise Magager, only when you sync from Windows Synchronization Manager. I guess as a last note, Microsoft has known about this problem for a year now but did not do enough testing of it to get it into sp3. I guess that we will have to wait until sp4 comes out or the next version of Sql Server.

Mixed environment x64 and x86 (compatibility)

I have all sql servers running 32bit. We need another SQL cluster and I would
like to install SQL2005 x64. My concerns are the compatibility between
SQL2000 32bit, SQL2005 32bit and the new one:
questions:
can I restore a x64 database to a 32bit SQL Server?
Anyone has had compatibility issues using a mixed environment?
If there is no difference, why there are different AdventureWorks versions
(x64 and x86) to download?
http://www.microsoft.com/downloads/details.aspx?familyid=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en
Microsoft says there is no problem, but I would like to hear some real
experience ..
thanks
Julio M
Hi
"Julio Mattos" wrote:

> I have all sql servers running 32bit. We need another SQL cluster and I would
> like to install SQL2005 x64. My concerns are the compatibility between
> SQL2000 32bit, SQL2005 32bit and the new one:
> questions:
> can I restore a x64 database to a 32bit SQL Server?
The backup file format is the same on both machines. The database file
format has not changed either, therefore you can move these from one platform
to the next without issues.

> Anyone has had compatibility issues using a mixed environment?

> If there is no difference, why there are different AdventureWorks versions
> (x64 and x86) to download?
> http://www.microsoft.com/downloads/details.aspx?familyid=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en
This is probably because of the samples being deployed on different platforms.

> Microsoft says there is no problem, but I would like to hear some real
> experience ..
You should deploy this because you need a platform that is better suited for
the 64 bit environment i.e. better memory usage, better processors etc.

> thanks
> Julio M
>
John

Mixed environment x64 and x86 (compatibility)

I have all sql servers running 32bit. We need another SQL cluster and I would
like to install SQL2005 x64. My concerns are the compatibility between
SQL2000 32bit, SQL2005 32bit and the new one:
questions:
can I restore a x64 database to a 32bit SQL Server?
Anyone has had compatibility issues using a mixed environment?
If there is no difference, why there are different AdventureWorks versions
(x64 and x86) to download?
http://www.microsoft.com/downloads/details.aspx?familyid=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en
Microsoft says there is no problem, but I would like to hear some real
experience ..
thanks
Julio MHi
"Julio Mattos" wrote:
> I have all sql servers running 32bit. We need another SQL cluster and I would
> like to install SQL2005 x64. My concerns are the compatibility between
> SQL2000 32bit, SQL2005 32bit and the new one:
> questions:
> can I restore a x64 database to a 32bit SQL Server?
The backup file format is the same on both machines. The database file
format has not changed either, therefore you can move these from one platform
to the next without issues.
> Anyone has had compatibility issues using a mixed environment?
> If there is no difference, why there are different AdventureWorks versions
> (x64 and x86) to download?
> http://www.microsoft.com/downloads/details.aspx?familyid=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en
This is probably because of the samples being deployed on different platforms.
> Microsoft says there is no problem, but I would like to hear some real
> experience ..
You should deploy this because you need a platform that is better suited for
the 64 bit environment i.e. better memory usage, better processors etc.
> thanks
> Julio M
>
John

Mixed environment x64 and x86 (compatibility)

I have all sql servers running 32bit. We need another SQL cluster and I woul
d
like to install SQL2005 x64. My concerns are the compatibility between
SQL2000 32bit, SQL2005 32bit and the new one:
questions:
can I restore a x64 database to a 32bit SQL Server?
Anyone has had compatibility issues using a mixed environment?
If there is no difference, why there are different AdventureWorks versions
(x64 and x86) to download?
http://www.microsoft.com/downloads/...&displaylang=en
Microsoft says there is no problem, but I would like to hear some real
experience ..
thanks
Julio MHi
"Julio Mattos" wrote:

> I have all sql servers running 32bit. We need another SQL cluster and I wo
uld
> like to install SQL2005 x64. My concerns are the compatibility between
> SQL2000 32bit, SQL2005 32bit and the new one:
> questions:
> can I restore a x64 database to a 32bit SQL Server?
The backup file format is the same on both machines. The database file
format has not changed either, therefore you can move these from one platfor
m
to the next without issues.

> Anyone has had compatibility issues using a mixed environment?

> If there is no difference, why there are different AdventureWorks versions
> (x64 and x86) to download?
> http://www.microsoft.com/downloads/...&displaylang=en
This is probably because of the samples being deployed on different platform
s.

> Microsoft says there is no problem, but I would like to hear some real
> experience ..
You should deploy this because you need a platform that is better suited for
the 64 bit environment i.e. better memory usage, better processors etc.

> thanks
> Julio M
>
John

Misterious Change of Compatibility Level in a Data Base

Hi everybody:

We have recently migrated our DDBB from SQL 2000 to SQL 2005 in several Servers. We have 2 DDBB per Server and the size of mdf files are between 10 and 40 GB.

We put Compatibility Level in 90 in SQL 2005 but when we arrive at work we see that our Maintenace Plans failed because the Compatibility Level of one of Data Bases changed to 70.

We have a Trace executing the whole day registrying the execution of stored procedure 'sp_dbcmptlevel' but in despite of Compatibility Level changes, the Trace does not registry anything.

Has anyone passed before me for this situation? Thank you in advance and greetings,

Nuria

After migrating (backup/restore or detach /attahc) to SQL Server 2005 have u changed the Comaptibility level? By default, the compatibility level will be 80. What was the compatibility leve of this database in sql 2000? check that. I assume that it was 70

Madhu

|||

your sql 2000 db probably would have had a compatability of either 80 or 70 (65,60 are not supported in sql 2005).......so once you restore it in sql 2005 it would be in the default compatability level as it was in sql 2000 unless you manually change it.......

|||

Yes, after migrating (attach in our case) to SQL 2005 we have changed the Compatibility Level to 90.

Not sure what was the Compatibility Level before migrating of this specific Server because we have 52 Servers in total; some of them had 65, others had 70 and other had 80.

The amazing thing is that Compatibility Level changes alone from 90 to 70.

|||

Yes, after migrating (attach in our case) to SQL 2005 we have changed the Compatibility Level to 90.

The amazing thing is that Compatibility Level changes alone from 90 to 70.

Missing Snapshot agents

Running Win2k & SQL 2K
This AM when I checked my SQL servers, I had a red 'X' on
the snapshot folder of my central server. When I
expanded it, there were no snapshot agents. I have 45 or
so publications on this server and know each one has a
snapshot agent.
HELP!!!!
How do I get them back?
TIA,
Larry..
check to see if you can find these jobs in the jobs folder. If you can't
these agents where never created. Something is very wrong.
If they are there, its a visibility problems. This problem is most likely
caused when you deploy the publication via a script and don't use unique
publication or snapshot agent names. your best bet is to drop all
publications and rebuild them. You could try to script them out and
carefully modify them so the publications have different names, and leave
the snapshot_agent and distribution_agent parameters blank.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:406b01c4aa1b$6a22f010$a601280a@.phx.gbl...
> Running Win2k & SQL 2K
> This AM when I checked my SQL servers, I had a red 'X' on
> the snapshot folder of my central server. When I
> expanded it, there were no snapshot agents. I have 45 or
> so publications on this server and know each one has a
> snapshot agent.
> HELP!!!!
> How do I get them back?
> TIA,
> Larry..
|||Hilary,
They are in the jobs folder. The snapshot agents also
are in the Publication folder for each publication. What
gives? Does it really matter that they do not appear in
the Snapshot folder? Dropping the publications and
recreatiing them is not an option. Any othere ideas?
Larry...
|||believe it or not, it really doesn't matter. You just don't have the
visibility when your snapshot agents fail, which isn't often.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
<anonymous@.discussions.microsoft.com> wrote in message
news:1e9a01c4aa38$941a0440$a501280a@.phx.gbl...
> Hilary,
> They are in the jobs folder. The snapshot agents also
> are in the Publication folder for each publication. What
> gives? Does it really matter that they do not appear in
> the Snapshot folder? Dropping the publications and
> recreatiing them is not an option. Any othere ideas?
> Larry...