Viewing 15 posts - 16 through 30 (of 32 total)
SQL Server Express does not have SQL Server Agent itself to run jobs. So, if you want to run a script periodically for SQL Server Express, then you will need...
April 7, 2010 at 12:37 pm
Using the backups from the production server, we have restored the databases to our development server >> have you restored the distribution database as well from "prod" into "dev"?
April 7, 2010 at 12:28 pm
Is the new "dev" server using the same distributor as the "production"?
If not, then overall you seem to be following the correct path. I wonder why would there be leftover...
April 7, 2010 at 12:27 pm
My problem now is that I am unable to get the initial snapshot to finish creating. We have a user in the agent that has permissions but when I look...
April 7, 2010 at 12:17 pm
You will have to write custom replication stored procs, specifically the sp_MSupd_<articlename> procedure. Replication allows to create and use custom code in the article's change propagating stored procedures, namely=INS_CMD, UPD_CMD...
April 7, 2010 at 10:25 am
Win, as he has stated, he (or any user from Server B) does not have access to server A (publisher and distributor). So, they cannot query the replication metadata tables...
April 7, 2010 at 10:17 am
I don't think I have understood why would replication cause any issues with SQL logins. Did you take a backup of publisher and restore it on subscriber while creating subscription?
The...
April 7, 2010 at 10:08 am
I don't have a code readily available but you can easily compare column values using simple LIKE operator since you are majorly doing string comparison. This can be done in...
April 7, 2010 at 10:00 am
Looks like data from the .bcp file (which contains the actual data) could not be imported correctly. Try re-running your snapshot agent to create a fresh snapshot and check if...
April 7, 2010 at 9:53 am
I will suggest not to try the LOG TRUNCATE_ONLY option. Rather, find a disk with enough space and take subsriber db backup and then shrink it. After this, set up...
April 7, 2010 at 9:48 am
You haven't specified if the distributor and publisher are on the same box. Anyway, the errors are there because sp_dropdistributor is trying to clean some leftover subscriptions and publications from...
April 6, 2010 at 3:23 pm
Based on what you are describing, it looks like the clustered SQL Server is publisher while standalone is the immediate updating subscriber. The immediate updating subscriber has _sync triggers to...
April 6, 2010 at 3:05 pm
Have you setup regular log backups at the subscriber site? If you set log backups, then the space in the transactions log will be reused and will stop the Log...
April 6, 2010 at 2:59 pm
You can easily check the article settings by querying the <publisher db name>..sysarticles table. Check the values of INS_CMD, UPD_CMD and DEL_CMD. You will have to do this in each...
April 6, 2010 at 2:51 pm
The disks that you are seeing in Windows are just volumes. The disk subsystem can have single or multiple disks to present a volume to Windows. So, if there are...
April 6, 2010 at 1:43 pm
Viewing 15 posts - 16 through 30 (of 32 total)