Viewing 15 posts - 166 through 180 (of 1,158 total)
No.
You could create a custom trigger on the msdb.dbo.sysjobs table to log when a change occurs.
December 4, 2013 at 9:26 am
As already stated, the tempdb is instance specific.
The only way to do something similar is to have 2+ instances and isolate them onto their own drives. You would still...
December 4, 2013 at 6:48 am
karim.boulahfa (12/3/2013)
MysteryJimbo (12/3/2013)
You're primary key (incident_id) is not set as an identity so you need to insert a unique value since you cannot have a...
December 3, 2013 at 8:05 am
Knight (12/3/2013)
If it was an identity column though surely you wouldn't receive this error.
Eureka! 😀
December 3, 2013 at 6:41 am
Knight (12/3/2013)
Perhaps you should be UPDATE'ing that field? Your INSERT statement implies you just want...
December 3, 2013 at 6:25 am
You're inserting a value into incident_ref.
You're primary key (incident_id) is not set as an identity so you need to insert a unique value since you cannot have a NULL primary...
December 3, 2013 at 6:24 am
I think the reason you have no replies is you aren't completely clear.
Replication does not drop tables on the publisher.
The default on the subscriptions is to "drop existing" and is...
December 2, 2013 at 2:48 am
How big are the tables? If the are each several GB each then I'd consider going with backup/restore then drop the extra tables.
If they are relatively small I...
November 27, 2013 at 8:03 am
I have a couple of powershell scripts which I can use to do this. I use them when I take over a role if there is little source control...
November 26, 2013 at 6:40 am
In theory this should work as a two stage process.
Restore the SQL server as the host using master and msdb recovery
Restore the distributor using the distribution db.
November 26, 2013 at 2:01 am
adams.squared (11/25/2013)
I have a table of 200,000 records. The natural primary key for this table is the combination of columns A1, B2, C3 and D4. I want to...
November 25, 2013 at 9:55 am
MysteryJimbo (11/25/2013)
This is good, as it means once recovered, the log reader will know everything that still needs to replicate.
I should have been clearer. You continue to stand a...
November 25, 2013 at 7:40 am
deep_kkumar (11/25/2013)
We have the latest backup of distribution database. But the data on publisher changes every minute
If you cannot restore the distribution db, you will have to reintialise...
November 25, 2013 at 7:02 am
If you plan on restoring the distribution db on the same distribution server you shouldn't need to cleanup replication on the publisher/subscriber. You would only need to do that...
November 25, 2013 at 6:58 am
Are there any distribution db backups? If so there is an MS article on how to restore it.
Will the data have changed on the published databases? If not, you...
November 25, 2013 at 4:55 am
Viewing 15 posts - 166 through 180 (of 1,158 total)