Access 2000 connected to SQL 2000
Is there a way to initiate Sql Replication via code from within Access?
All Replication jobs are setup to run on demand. I would like to be
able to click a command button in Access to start the jobs.
Can someone point me in the right direction?
Thanks
Dale
Hi.
View 2 Replies View RelatedMy problem is the following: when I try to configure replication between two SQL servers, I get an error message even before I get a chance to configure anything. When I choose "Configuring publishing and subscribers" (in Enterprise Man.) I receive the following error message: "SQL Server Enterprise Manager could not complete the wizard because @@SERVERNAME is for " is NULL. Use sp_addserver to set @@SERVERNAME".
When I try to do this I get the message that the name already exists...
Something is obviously wrong with this server, but I can't pinpoint the problem, much less resolve it - I would very much appreciate any help!!
Regards / Per
Hi guys,
I am new to SQL Server 2000 and like to enquire the following.
Scenario:
this current website is hosted by A but now taken over by B.
B was given SQL server username and password and was instructed to download the database directly from A based on the username n pw given.
So my qns is:
Is it possible to initiate data transfer from one server situated at locationA to another server at locationB that doesnt belong to the same domain? If can, by which ways? Using the DTS method? Or there are some settings to be configure at ODBC in order to initiate the data transfer?
Any experts out there? ;)
HiIs it possible to force row level locking in one or more tables insome database. We have some problems when SQL Server decides to choosepage- or table-level locking.We are using SQL Server 2000.Best regardsAarno
View 1 Replies View RelatedI am trying to initiate a Netbackup task from a SQL Job using the following CmdExec code:
"C:Program FilesVERITASNetBackupnindbbackex.exe" -f "C:Program FilesVeritasNetBackupDbExtMsSql<Filename.bch>" -p <profilename> -u <username> -pw <password> -s <server> -np
If I run it from a Command Prompt window it works fine, however if I copy the exact same code into a SQL Job and use the job type 'Operating System (CmdExec)' it fails to run. All I get in the Job History is: "Executed as user: DomainUsername. The step did not generate any output. Process Exit Code 2. The step failed."
I have managed to get this to work on another almost identical server using the same accounts and everything but for some reason it won't run on the one I'm currently using.
My question is two fold. First, What is the best method for mirroring to a fail-over server? Replication has limits on tables that do not have key fields, and I am finding that Log Shipping is harder to work with.
I have set it up several times, and conducted tests with test databases, but when it fails, I get no indication as to why, and I also can find no way to re-initiate it (without deleting the maintenance plan and starting over). Which leads to my second question, is there a way to manually initiate a log shipping plan already defined?
Thanks in advance!
Rollin
Say i create a mirroring for a database without witness server, if the principal server is offline, can i make the mirroring database online?
thanks in advance.
This is a solution for a very specific problem, and it's one that you'll hardly ever use, but it's important to know about that one scenario where it can save your neck. Ordinarily, stored procedures are only recompiled if they're no longer in the procedure cache. But if a stored procedure's execution plan is still in the cache, then SQL Server reuses the compiled storedprocedure and its existing execution plan. This is almost always the best course of action. Almost always, but not always.Sometimes, however, reusing an existing plan doesn't offer the most efficient performance. Imagine, for example, that your stored procedure accepts a parameter that determines the natureof a JOIN operation. The results can vary in a big way, so you wouldn't want your procedure to be locked into an execution plan that might be completely inappropriate for that JOIN. In a highlyspecialized case like this, you might want to force SQL Server to recompile the procedure every time the procedure runs. Doing so comes at a performance cost, but this might be offset by thesavings you gain in not executing the procedure with an awful compiled execution plan. Consider carefully whether to use this approach (or whether to re-engineer the over-design of yourapplication to avoid this situation in the first place). Should you need to instruct SQL Server to recompile each time, add the WITH RECOMPILE directive to the procedure, like this: CREATE PROCEDURE ProcName @Param int /* ... other parameters */ WITH RECOMPILE AS /* ... procedure code follows */
If we omit "WITH RECOMPILE", what will be the consequence? Thanks
Is there an open APISDK for sharepoint's power pivot galleries allowing on demand processing of a power pivot model over there? Ideally from a SSIS package?
View 4 Replies View Relatedi went through the documentation but i was not clear on following, here is the scenario :-
a Central server is having SQL Server 2000
3 Remote Locations :- Each having 4-5 no of computers, connected on a Lan, and on one of the machines MSDE 2000 will be running.
My Questions are :-
1. Can remote locations, update data locally and send changes (say in every one hour) to central server. If yes, then how ??
2. Same way they can receive updates from Central Server on whatever was updated on Centra Server or on the 3 remote locations. If yes, then How ??
any help will be highly appreciable.
Hi,
I have no idea of SQL2000.Can anyonetell me steps /precuations involved in going for Replication in SQL2K.
Also,How do we do log shipping in SQL2K?
TIA
pd
I am trying to set up transactional replication (not immediate updating) via a push subscription between a SQL 7.0 Server and a SQL 2000 Server. The SQL 7 server is the Publisher / Distributor, and the SQL 2000 server is the subscriber. Replication will not work between the two, I have removed then setup replication to no avail. The SQL 7 server always reports that it can't connect to the SQL 2000 server. Same problems the other way if I try a pull subscription.
Anyone have any ideas?
thanks,
Kyle Freeman
zilchfrag@zilchfrag.com
I'm trying to replicate a sql 7.0 table to a sql 2000 server. Does anyone know how I can register a sql 2000 box through Ent. Manager onto 7.0? I've been told that I need to upgrade my production server's Ent. Manager to 2000 but I not sure if that is a real safe bet. Can anyone give me any insight to this?
Thanks,
Jeff
I am trying replication on sql 2000
I want to do replication using two databases. suppose say Db1 and Db2
if new record is added in db1.table1 then the same record should get added to Db2.table1 and vice versa.
using enterprise manager I have successfully created replication from Db1 to Db2.
how to do it from Db2 to Db1?
any suggestion would be helpful.
thanks
How do I know whether the record in a row was insert,update and delete that replicated to a subscriber?
Is there a flag or an indicator in msmerge_contents,msmerge_tombstone ,msmerge_genhistory tables or any other msdb/replication system tables?
I would like some simple input on achieving true two-way replication with SQL 2000. We have need to load balance our website between two sites and since it is SQL based, would need to have dual DB servers at each site with two-way replicated data. They would need to be replicated at real-time. Will the built in SQL replication tools work OK? Has anyone done this? Thanks in advance.
View 1 Replies View RelatedHere is what we are trying to solve:-We have a SQL 6.5 server (version 6.50.258) we will call SQL65-A, onan NT 4.0 machine (version 4.00.1381), on Domain-A-We are trying to replicate directly to a SQL 2000 server (version8.00.818) we will call SQL2000-A, on a Windows 2000 machine (version5.00.2195), on Domain-B-We also have a SQL 6.5 server we will call SQL65-B in Domain-B-The domains are trusted-We get the error that it cannot connect to the SQL 2000 server whentrying to replicate, even though I can register the SQL 2000 server asa Remote ServerThe work-around we have right now is replicating from SQL65-A toSQL65-B, then using SQL65-B as a subscriber as well as adistributor/publisher to SQL2000-A.
View 1 Replies View Relatedsql 2000 replication: Is there a way of getting tables to replicate without them having a pramary key?
View 1 Replies View RelatedHello.
We've a SQl Server 2000 with a DB with 4GB.
Now we need to reply our server with another server that will be connected with us for comunications.
We want that the replicacion is on-line.
Can you recommend me if we upgrade the servers to SQL 2005?
Does this replicacion process consume many resources of the server?
Which the requirements hardware minimum are for this process?
As much wide of band for the comunications I can need?
Thanks.
A greeting.
Hi,
I wantked know the best tool or way for Replication between SQL server and DB2/IBM(MVS).
Thanks,
Ravi
Hi guys.
I have two scenerio.
One:
Two servers (SQL 7.0), transaction replication
Two:
Four servers (SQL 7.0), transactional replication one publisher, one distributor and 2 subsribers.
I need to upgrade these two scenerio to 2000.
Please advice me with suggestions and your experience.
Is Online replication possible?
-MAK
Hi,
I am in between of analysis for Upgradation of SQL server 7.0 to SQL server 2000.
I have few server on SQl server 7.0
I wanted to know , is the replication supported between SQL server 7.0 and SQL server 2000.
a ) from SQl server 2000 to SQL server 7.0
and
b ) from SQL server 7.0 to SQL server 2000.
Both this scenarios will exist.
Thanks in advance
Vikram
Hi Friends
What are the main differences between Sql Server 2000 Replication and Sql server 2005 Replication?
Thanks
Vic
I doing a transactional replication with two servers. Server A, the Publisher and Distributor. Server B, the Subcriber. I did the replication using a dummy DB for practice purpose and it works fine. When I try to implement the replication in original DB, I found that some tables don't have primary keys and to be able to implement transactinal replication all the replicated tables need to have a primary key. I want to add the primary keys to those tables and also implement the replication but the problem is those tables have data in it. I'm thinking in create the new table and do a DTS to import the data to the new table or it's fine just to modify the table in design to add the primary key "Those table have record in it".
Some of you have any advice to me?
Hello,
I am using MSDE 2000 for replication of my Data. I have one publisher and two subscribers. but i need t filter rows for publications. Problem is that for filtering, i need host_name and in push replication host_name is name of system in which Agents are running but in MSDE all agents are running in publisher system ( distributor System). so everytime for any publication i get only id of server.
i am facing same problem in pull replication also.
Regards,
Any suggestions on how to replicate from AS/400 to SQL Server 2000?
Data is stored on a AS/400, but applications use a SQL Server 2000 DB. Currently, DTS packages drop the SQL DB, rebuild the tables from a script, copy the data, and then rebuild the indexes as a nightly batch job. Is there a better way to do this? Also is there a clean way to replicate daily transactions as well?
Hey everyone,
This may be in the wrong forum, but I have a database in SQL Server SP3a that I will be replicating out to SQL Mobile 5.0. The setup of the replication will not be a problem, however, once replication is setup, I will have to change the DTS Package that creates these tables.
I have created a DTS Package that drops the tables and recreates them from a DB2 database. My problem is that I won't be able to drop these tables once a publication has been established.
I really don't need to drop the tables if I can create a script to pull just the new records from the DB2 database.
Does anyone know of an easy way to do this? Are there any products out there that would make this easier? Has anyone else out there had to create a publication with this scenario?
Just a little background, I originally created the DTS Package from an import, and then modified it. I added the DROP TABLE scripts so that I wouldn't just append the same data over and over. Perhaps there is a better way of doing this than a DTS Package.
This would probably be a lot easier to handle if I weren't pulling from a DB2 database because I would probably be able to create a trigger or something on the source database, however I know nothing about DB2 datasets other than how to pull the data out. I would appreciate any input on this.
Thanks,
Lee
Hi
I'm trying to determine if it is possible to do many to many replication in sql server 2000.
What i basically want is to have n databases share the same basedate (share a common database) and allow updates in any database to be replicated to all the other databases (with a simple conflict resolution, like last update wins).
My goal is total autonomy, without a single point of failure. If any node goes down, the other nodes will continue to work and continue to replicate their data to the remaining nodes. When a node comes back up it will catch up with the over nodes (or get reinitialized if it was a serious crash).
The amount of data i want to replicate is not that big (less than 100MB) and does not change that often. All servers are sql server 2000 instances connected by a gigabit network and the number of nodes involved is less than 10. Some latency is also acceptable.
the question is: is this at all possible? I have read i bit in 'SQL Server High Availability By Paul Bertucci' and some other resources and it looks like a multiple publishers or multiple subscribers with merge replication setup should work, but i'm not too sure if it will work for n > 2 nodes (where all nodes publish and subscribe to each other) and it also mentions constraints on which data a given node is allowed to update (i hope this could be handled by simple conflict resolution).
And if it is not possible in 2000, could it be accomplished en 2005?
TIA Jens
I have been trying to get a SQL 2000 server replicated with another - and keep getting the same error:
SQL Server Enterprise Manager could not configure "Server Name" as the Distributor for "Server Name"
Error 18483: Could not connect to server "Server Name" because 'distributor_admin' is not defined as a remote log in at the server.
I found several sites that helped me to get some feedback - but I am still hitting the same error.
Any thoughts would really help now.
Thanks!
M
Hi,
Can anyone help me?
How do I implement SQL Server Replication?
Where, and how? Do I have to download specific software to do this, or how?
What would be the right option?
Thanks
SJB
Is it possible to replicate from Oracle to SQL Server.
Thanks,
Bianca
hi, i was trying to use a merge replication between 3 SQL 2000 Servers.
The problem is that the replication process generate to many data conflicts and i dont know why, because in the others 2 servers was nobody.
only 1 users have active users the others doesnt have anyone yet, if no updates and no inserts were made in the other 2 servers, why the conflicts?
the server have Win 2000 Server.