Viewing 15 posts - 19,741 through 19,755 (of 59,098 total)
Mike Dougherty-384281 (8/28/2015)
Can't we have whatever triggering event send a link for a full-featured data explorer to our preferred communication provider (email/sms/tweet/etc)? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2015 at 4:06 pm
Why not just do a [font="Courier New"]SELECT SizeMB = Size/128.0, * FROM sys.Master_Files [/font]and call it a day?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2015 at 2:22 pm
ScottPletcher (8/28/2015)
Yes, much care needs to be taken before allowing anyone to run ad-hoc queries....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2015 at 11:21 am
jeffrey yao (8/28/2015)
But from pure technical perspective, I feel there is one special deficiency I do not like,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2015 at 11:07 am
Heh... you guys are all missing it. You should encourage all manner of ad hoc queries from the masses so that you can better justify a massive hardware and...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 9:48 pm
jay-h (8/27/2015)
After we demonstrated that the db from the previous version was much faster on the same server, now suddenly, the vendor stopped saying "it must be your server" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 9:43 pm
Heh... stop it. Stop writing T-SQL in Excel macros. Write a stored procedure or the appropriate view in SQL Server, dedicate 2 well marked cells in Excel as...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 9:18 pm
I guess it depends. Supposedly, if you can prove how you tested, you can be certified. I personally don't think it's worth the time to do it ourselves....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 9:13 pm
32 CPUs * 6 hours = 192 hours available CPU time.
135/192 = 70.3125% of all the CPU time was dedicated to that one task.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 9:01 pm
diegosiao (8/27/2015)
To a "from zero" robust corporative application, I think code-first oriented modeling is a good approach, taking advantage of the SQL script generation to revise it and then...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 8:52 pm
Don't do this in SQL Server. Do it in Windows. Please see the following KB.
https://support.microsoft.com/en-us/kb/324796
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 8:12 pm
mike 57299 (8/27/2015)
or is it
Restore Full
Restore D3
Restore L1 - L8
Yes. That's it.
What happens if D3 is corrupt?
Restore FULL
Restore D2
Restore L1-L24 for D2
Restore L1-L8 for D3
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 8:02 pm
Benki Chendu (8/27/2015)
I have a server with 2 processors, 12 cores each making it a 24 core logical system.
My tempdb has 4 datafiles and 4 logfiles created.
I know creating more...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 7:52 pm
chandrika5 (8/7/2015)
Update mytable
set col1= 'some value',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 7:43 pm
craig.bobchin (8/27/2015)
ScottPletcher (8/27/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2015 at 7:39 pm
Viewing 15 posts - 19,741 through 19,755 (of 59,098 total)