Viewing 15 posts - 24,811 through 24,825 (of 59,099 total)
The best way would be to write the reports to return the correct timeframe rather than relying on the time that they are executed.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 1:11 pm
Solomon Rutzky (1/8/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 12:56 pm
rodjkidd (1/8/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 12:45 pm
george sibbald (1/8/2014)
select 'alter database ['+name+']...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 12:42 pm
satishchandra (1/8/2014)
Thank you Sean for your inputs/suggestions.
Your suggested solution was close too, but I was looking for traversed...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 11:30 am
Todd Erickson (1/8/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 11:26 am
SQL Guy 1 (1/8/2014)
DBCC shrink file did not help. First, it shrinks entire file which also has other tables. And it shrank just little...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 11:20 am
george sibbald (1/8/2014)
run a dbcc shrinkfile on it, you'll have all the fragmentation you want.
+1
but not in production 🙂
+1000!!!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 11:14 am
Sean Lange (1/8/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 11:10 am
Sridhar-137443 (1/7/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 8:29 am
karthik babu (1/8/2014)
DBCC sqlperf...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 8:24 am
VERY nice, Solomon. Great job!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 8:08 am
Ya just gotta love the "old ways" sometimes. 🙂 Before we get into that, let's build a bit more test data. This first time around, we'll do it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2014 at 7:35 am
pmadhavapeddi22 (1/7/2014)
I tried the below solution, will it effect the peformance ?
select
employee.employee_id ,date_joined ,aa.date_ , ROUND((sal+due_amount),2)
from employee
inner join (select employee_id,date_joined,MAX(date_) 'date_' from employee group by employee_id, date_joined)aa
on...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2014 at 8:08 pm
Luis Cazares (1/7/2014)
Jeff Moden (1/7/2014)
eccentricDBA (1/7/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2014 at 5:20 pm
Viewing 15 posts - 24,811 through 24,825 (of 59,099 total)