Viewing 15 posts - 9,646 through 9,660 (of 39,880 total)
ArnoKwetters (6/22/2015)
infinite loops. My exec of the SP stops already after 32 loops.
That's the limit for depth of calls in a stack.
June 23, 2015 at 10:17 am
Is this merge replication? I haven't spent a lot of time there, but is there a log you can check to see what's causing the jobs to fail? It sounds...
June 23, 2015 at 9:13 am
this makes no sense without years. Are you saying that you'd need Jul '14 through Dec '14 and then Jan '15 through Jun '15?
Or are you saying a rolling year...
June 23, 2015 at 9:09 am
What you could do is set up a baseline of how things perform now. Then implement a small replication system, maybe a single table/article that has enough activity to show...
June 23, 2015 at 8:52 am
Is this a default instance?
June 23, 2015 at 8:50 am
Big is all relative. The title here is about "big data", which is an overloaded, hyped term meaning multiple things from JSON structured data to lots of text files.
June 23, 2015 at 8:49 am
There's a DMV as well: https://msdn.microsoft.com/en-us/library/ms190484.aspx
We have an article as well: http://www.sqlservercentral.com/articles/T-SQL/77057/
June 23, 2015 at 8:48 am
SP1 had a SSDB Catalog issue. It was corrected and re-released.
However, there is a CU1, but it has lots (100+) fixes. I'd go with SP1 for now. Seems stable.
YMMV
June 23, 2015 at 8:44 am
chrisn-585491 (6/23/2015)
June 23, 2015 at 8:43 am
TomThomson (6/23/2015)
June 23, 2015 at 8:41 am
emmchild (6/23/2015)
June 23, 2015 at 8:38 am
This is exactly what DLM Dashboard was designed to do. Catch changes in schema. It works well for me in small projects here.
Disclosure: I work for Redgate.
June 23, 2015 at 8:31 am
Viewing 15 posts - 9,646 through 9,660 (of 39,880 total)