Viewing 15 posts - 16,681 through 16,695 (of 59,067 total)
joshua 15769 (10/6/2016)
I do have to sometimes say "NO" to something but I'm normally able to suggest an alternative and the reason why the alternative is better.
This is what a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 9:37 pm
ALTAIR SOUZA (10/6/2016)
ALTER DATABASE msdb SET NEW_BROKER WITH ROLLBACK IMMEDIATE;
In sys.databases column is_broker_enabled will be set to 1 and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 9:02 pm
Or use a real splitter.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 8:59 pm
rsampson (10/6/2016)
conditionally delete file, done.
Works great if the directory is not empty, barfs a warning, then fails...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 8:33 pm
RVO (10/6/2016)
I talked to DBA.
They are planning to partition {Pink} table
and created these partitions as placeholders.
They partitioned {Poink_parttioned} tables will be moving data to {Poink}...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 7:06 pm
Alan.B (10/6/2016)
SELECT Id ,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 6:59 pm
ankur_libra (10/6/2016)
Please also monitor following on databases involved:-
1. Index Fragmentation
2. Statistics Update
3. Blocking to ensure that jobs are not being blocked by any oher process
4. I/O & Waitstats (As...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 6:31 pm
Brandie Tarvin (10/6/2016)
This doesn't affect me because I'm on "high ground".
Isn't that where it's most windy? :blink:
I hope everything turns out ok. You guys be safe.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 5:15 pm
Hugo Kornelis (10/6/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 5:12 pm
If you're using SQL Sever 2012 or above, you shouldn't be using the "Quirky Update" method... period. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 5:05 pm
Gary Varga (10/6/2016)
Jeff Moden (10/5/2016)
...I do have to sometimes say "NO" to something but I'm normally able to suggest an alternative and the reason why the alternative is better...
I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 9:03 am
hegdesuchi (10/6/2016)
Hi,My colleague finally helped me with this. Problem was with web service connection wasn't closed. He asked me to use this
Soapclient.close().
This seemed to work.
Thank you!
Great. Glad...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 8:50 am
I'm interested in the problem but don't know the solution. Bumping this post for you. Hopefully, someone else may have some information on the problem. Be prepared...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 6, 2016 at 8:27 am
komal145 (10/5/2016)
i have check other tables and do lot of stuff to get this point . So , i have to do it in ssis.
Not really. You can...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2016 at 8:30 pm
It's a funny thing... sometimes so called "DBA Syndrome" is the fault of the DBA. Sometimes it's actually because of "Developer Syndrome" like the one at a previous job...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2016 at 8:23 pm
Viewing 15 posts - 16,681 through 16,695 (of 59,067 total)