Viewing 15 posts - 9,106 through 9,120 (of 59,091 total)
Also, you can implement compression (page or row) and get indexes smaller + less I/O and wiser RAM usage. Thanks to Kalen Delaney for the ported version of standard...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2019 at 2:23 am
Ummmm.... is that where the decisions to not include critical functionality or "not good enough but we have a schedule to meet" decisions are cast in stone?...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2019 at 11:18 pm
With the new SSC, everything is supposed to run through a dev/QA cycle before prod. We have PRs that require review before they get merged into a deployable spot....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2019 at 6:59 pm
Hi,I'm pretty new to Azure but less new to SQL Server. We have an Azure SQL database with one table of about 300000 rows. So not huge. But, whilst...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 26, 2019 at 3:31 pm
From the article:
Flash storage is known for enabling significant improvements in data processing operation speeds, allowing multi-terabyte databases to be stored "in-memory", with a read/write speed that is four...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2019 at 1:40 pm
Please see the following articles. The first compares PIVOTs to an old "Black Arts" technique known a CROSSTAB (as well as fully explaining CROSSTABs), which is what Erland is talking...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2019 at 11:55 am
Jeff, You ask some great questions. Are you suggesting that I create a separate database with only views (that are named with the original names of the tables I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 21, 2019 at 11:47 am
If prod is on a SAN, a lot of SAN vendors provide the ability to do "SAN Snapshots", which are virtually instantaneous.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2019 at 8:38 pm
I guess what I'd really like to know is why do you have the second set of fully replaceable tables to begin with? What are in these tables and why...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2019 at 1:51 pm
Hi, It might be worth looking at Partition Switching as a possible option as well: https://www.jamesserra.com/archive/2012/07/sql-server-table-partition-switching/
How will partition switching help you between databases?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2019 at 1:47 pm
Jeff, thank you for all the info and your time it's greatly appreciated!
--Jeff Moden
Change is inevitable... Change for the better is not.
June 20, 2019 at 5:07 am
You can also use a computed column for as_of_month, there's no need to physically store it again. as_of_date date NOT NULL, as_of_month AS CONVERT(varchar(6), as_of_date, 112), That...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 19, 2019 at 9:07 pm
Be honest, was this one of you? https://www.newsweek.com/drunk-poland-soviet-tank-1444475
Not me... but I want one.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 19, 2019 at 9:03 pm
I'm pretty sure that a Tally table solution for this wouldn't be the preferred solution. There is a set based solution. See the winning entry at the bottom of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 19, 2019 at 7:56 pm
Thanks for the update, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 19, 2019 at 7:48 pm
Viewing 15 posts - 9,106 through 9,120 (of 59,091 total)