Viewing 15 posts - 20,671 through 20,685 (of 59,072 total)
bray_tim (5/17/2015)
The deadlock victim is running at the serializable isolation level. Are you sure you need this. I would suggest READ COMMITTED.
Before everyone drops a ton of bricks on you...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 8:49 pm
How often do you want to synchronize the DDL? Are you also looking to synchronize the data? If so, how often?
Can the changes be "destructive" as in total...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 8:45 pm
TomThomson (5/17/2015)
Jeff Moden (5/16/2015)
Me: ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 8:13 pm
naga.rohitkumar (5/16/2015)
our environment has 2008 and 2005 sqlservers and they are standard versions in that case how can...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 7:56 pm
It's a funny thing... If most people took the time to lookup the real original definition of "geek", they'd never use the word ever again.
It's also funny that "hacker" was...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 6:59 pm
I'm amazed at this question for 2 reasons...
1) The coverage for such a question in Books Online is not obvious. You actually have to infer that such a capability...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 4:26 pm
craig.budd (5/17/2015)
I have got it working with the following script.
create table #temp (Value varchar(500), Number int)
insert into #temp
(Value, Number)
select Source, (select charindex('\', reverse(Source))) from Table
select * from #temp
select distinct(left(Value,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 7:59 am
Heh... I look at the recommendations for "scripting" languages with a bit of disgust. There are so many things that SQL Server does very well through T-SQL but people...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 7:57 am
Agreed. I guess that's what I'm griping about. They don't actually know how to test for what or that "what" even exists.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2015 at 6:57 am
TomThomson (5/14/2015)
Jeff Moden (5/13/2015)
TomThomson (5/13/2015)
Jeff Moden (5/11/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2015 at 10:39 pm
Jeff Moden (5/9/2015)
sanjarani (5/9/2015)
One of many SQL Servers features that is hardly ever used because alternative methods are more suitable.Please explain your "alternative methods" and how they are "more suitable".
What...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2015 at 10:36 pm
It's never too late for such advice.:w00t:
And I have to agree... if you can actually get a 50% query performance increase by changing hardware, you're pretty lucky.
Performance is in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2015 at 10:27 pm
Nah... we all take turns learning from each other. To coin a phrase, "I learn from you, you learn from me, and people learn from us and that's good...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2015 at 10:15 pm
Igor Micev (5/14/2015)
Just to share with the sql folks that the problem was resolved by upgrading the instance with CU1 and CU2. Now there is no issue with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2015 at 9:59 pm
Eirikur Eiriksson (5/16/2015)
shivakumar.623 (5/14/2015)
My database was crashed then How to identified in particular server particular database was crashed
Quick question, (and piling on the previous questions) can you tell us what...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2015 at 9:46 pm
Viewing 15 posts - 20,671 through 20,685 (of 59,072 total)