Search results for query: *

Have you checked your licensing for the SQL Server on your Network? Is it set Per Seat or Per Server? What version of SQL Server 7.0 are you running (Full or Desktop)? I would imagine that you have the Licensing set Per Seat. What tkind of replication scenario are you running?

Run the following query in the Query Analyzer: select @@servername This will check if SQL Server recognises its name. If not, this would return a null. Microsoft recommends reinstalling SOL Server to fix the problem. However, there is an easier method located here in the Forum. If I can come...

We recently had to disable the Replication Process, dropping all subscriptions and disabling the publisher. The system was down for three days. When we re-setup Replication, creating a new publication and adding the subscriptions, and synchronised "No data needed to be merged.&quot...

I have a problem with an existing Merge Replication. We recently had to disable the Replication process, dropping all subscriptions and the publisher. This was down for three days. When we re-setup the Replication and synchronised 'No data needed to be merged.' However, during the down time, the...

You could try backing up the Database to a new location, but you would have to create the folders in the new location, i.e Mssql7/Backup and Mssql7/Data in the new location. When you restore the database, you can select the path in the Options Tab and this should tag the database to this new...

One of the problems I encountered in setting up a Merge between two servers in different locations is that you need to set-up an OS_Shell Job to dial-up. This requires Windows NT to have access to the Schedule Service. Check to make sure that the Schedule Service is active and set up an Account...

Merge Replication is in use. However, this has to be manually sychronised every day. How do you automate dial-up from SQL Server 7.0 to allow merge to take place?

How do I automate Replication over a dial-up network