Viewing 15 posts - 46 through 60 (of 496 total)
No, it is not, but I an not maxing out the CPU or I/O. Besides, the edition is different: the production is SQL Sever 2008R2 Ent, in test is...
June 11, 2014 at 12:32 am
The problem is, if you hardcode the clock move dates, you may get it wrong, as Australian government sometimes changes those dates.
The server timezone is (UTC-06:00) Central Time (US &...
May 27, 2014 at 1:17 am
Eirikur Eiriksson (5/26/2014)
Roust_m (5/26/2014)
To deal with clock moves.Bear with me here, but why not do this in TSQL as a set based operation?
Can you please elaborate on this? ...
May 27, 2014 at 12:18 am
All Litespeed versions would restore native backups btw, it is a matter of it the version is current enough for the SQL Server version. Version 5 is not compatible...
February 3, 2014 at 5:05 pm
JohnFTamburo (2/3/2014)
Roust_m (2/2/2014)
I need to be able to restore some native compressed backups with litespeed. The reason being, we have very complex test environment build process and want to...
February 3, 2014 at 4:05 pm
free_mascot (6/26/2013)
Try to capture error through profile.
Which profile?
June 26, 2013 at 7:24 pm
Andrew G (6/26/2013)
Interesting, so it's a load issue with the distributor? Did you change to a pull subscription or update the jobs to use cmdexec?
I did cmdexec. Very...
June 26, 2013 at 7:24 pm
This turned out to be the problem:
Just migrated to the new cluster, did not change the replication architecture. Everything worked on the old one.
June 26, 2013 at 1:31 am
WolfgangE (6/22/2013)
Roust_m (6/20/2013)
The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.
Locate the SQL-Job in management studio (not within the replication...
June 22, 2013 at 8:44 am
Yep, I did check the replication monitor. And this query returns errors which happened two days ago and had been fixed.
Amazingly, the snapshot agent works fine when run...
June 22, 2013 at 7:30 am
It turned out that UDP port 1434 was blocked. Once unblocked, the problem was resolved.
June 4, 2013 at 1:27 am
They are on the same domain, but servers A and C are in a different subnet from server B.
June 3, 2013 at 12:52 am
It is SQL cluster name and I can connect to that instance from another server with no problems.
Let me try to explain it in a different way:
I can't connect from...
June 2, 2013 at 11:53 pm
Viewing 15 posts - 46 through 60 (of 496 total)