TRIPLE CROWN: DCAC WINS 3RD YEAR IN A ROW AT AMERICAN BUSINESS AWARDS

Published On: 2021-04-30By:

OCEANSIDE, CA, May 4, 2021 – For the third year in a row, the American Business Awards® honored the information technology experts at Denny Cherry & Associates Consulting [DCAC] with two Stevie’s including:

  • Gold for IT Company of the Year
  • Bronze for Tech Professional of the Year (Kerry Tyler)

More than 3,800 nominations – a record number – from organizations of all sizes and in virtually every industry were submitted this year for consideration in a wide range of categories at the American Business Awards and more than 250 professionals worldwide participated in the judging process to select this year’s Stevie Award winners.

IT Company of the Year

DCAC’s revolutionary Power BI telemetry and data visualization design on behalf of a real estate publisher, as well as DCAC’s impressive 96-hour rescue of a client in the aftermath of a Ransomware attack as stood out for IT Company of the Year. Judges cited:

“Love the business model. Sounds like you’ve got yourselves a squad of smoke jumpers there. Great list of successes resulting from your engagements.”

“Denny Cherry & Associates Consulting company is an emerging cloud solutions company.”

Tech Professional of the Year

Renowned Microsoft and VMware expert and DCAC veteran Kerry Tyler also won bronze for “Technical Professional of the Year.” Judges stated, “Kerry simply goes above and beyond to address customers.”

DCAC Founder Denny Cherry commented, “Winning is always great, but winning this year is defying the odds. The 2020 pandemic required more innovation and stamina from the entire Information Technology industry than the past decade combined, so this moment is truly humbling. We thank the judges, and I personally want to thank my team. I couldn’t be prouder to work with you.”

About Denny Cherry & Associates Consulting
Award-winning Microsoft Partner and Gold Platform certified Denny Cherry and Associates Consulting assist companies with reliably attaining IT goals such as Azure Migration, HA, scalability, SQL Server virtualization and acceleration, while finding ways to save on costs. With clients ranging from Fortune 50 corporations to small businesses, their commitment to each is the same: to provide a deft, high-speed IT environment that maximizes every aspect of their platform: from architecture, to infrastructure, to network.

About the American Business Awards®
Stevie Awards are conferred in eight programs: the Asia-Pacific Stevie Awards, the German Stevie Awards, the Middle East & North Africa Stevie Awards, The American Business Awards®, The International Business Awards®, the Stevie Awards for Women in Business, the Stevie Awards for Great Employers, and the Stevie Awards for Sales & Customer Service. The Stevies also produce the annual Women|Future Conference.  Stevie Awards competitions receive more than 12,000 entries each year from organizations in more than 70 nations. Honoring organizations of all types and sizes and the people behind them, the Stevies recognize outstanding performances in the workplace worldwide. Learn more about the Stevie Awards at http://www.StevieAwards.com.

Contact the Author | Contact DCAC

DCAC Wins Gold at the American Business Awards for the 2nd year in a row

Published On: 2021-04-29By:

Denny Cherry & Associates Consulting is thrilled to announce that we have won two awards from the American Business Awards.

ABA Gold Award

DCAC was named as “IT Company of the Year” with a gold award in this category, with this win being our second gold award in this category in a row. A judge for this award stated “Love the business model. Sounds like you’ve got yourselves a squad of smoke jumpers there. Great list of successes resulting from your engagements.”

ABA Bronze Award

Kerry Tyler ( b | t ) was also awarded the Bronze award in the “Tech Professional of the Year” category. A judge for this award stated, “Kerry simply goes above and beyond to address customers.” And we couldn’t agree more.

Our outsourced Marketing team, who works with a variety of companies in a variety of industries has never had a client win gold in the Company of the Year category twice in a row before saying “You’re the first client I’ve ever had win gold for Company of the Year for two consecutive years — in the IT category no less when it is always the most competitive.”

The entire team at DCAC is incredibly proud to have won the Company of the Year award. And Congrats to Kerry Tyler ( b | t ) for winning this award. This is the third year in a row that a member of DCAC has been awarded a Tech Professional of the Year award with prior awards going to Joey D’Antoni and Monica Rathbun.

Our plan is to keep up the pace for 2021 and show well in these award categories next year as well.

The full list of awards that the team at DCAC has been awarded can be found on our awards page.

Denny

Contact the Author | Contact DCAC

Altering a Computed Column in a Temporal Table in Azure SQL

Published On: 2021-04-22By:

System-versioned temporal tables were introduced in SQL Server 2016. They provide information about data stored in the table at any point in time by storing an effective dated version of each row rather than only the data that is correct at the current time

You can alter a temporal table to add or change columns, but you must first turn off system versioning. Let’s look at an example.

CREATE TABLE [dbo].[DatabaseSize](
	 [DatabaseID] [varchar](200) NOT NULL 
	,[ServerName] [varchar](100) NOT NULL
	,[DatabaseName] [varchar](100) NOT NULL
	,[SizeBytes] [bigint] NULL
	,[SizeMB]  AS ([SizeBytes]/(1048576))
	,[ValidFrom] [datetime2](7) GENERATED ALWAYS AS ROW START NOT NULL
	,[ValidTo] [datetime2](7) GENERATED ALWAYS AS ROW END NOT NULL
	,PERIOD FOR SYSTEM_TIME (ValidFrom, ValidTo)
	,CONSTRAINT PK_DatabaseSize_DatabaseID PRIMARY KEY CLUSTERED (DatabaseID)
) WITH (SYSTEM_VERSIONING = ON (HISTORY_TABLE = [dbo].[DatabaseSizeHistory]));

Temporal tables must have a primary key defined. They also must contain two datetime2 columns, declared as GENERATED ALWAYS AS ROW START / END. The statement above creates both the current table and a history table.

The history table has the same schema as the current table, with one difference: the SizeMB column in the history table is not a computed column.

The dbo.DatabaseSize table is a system-versioned table. The DatabaseSizeHistory table is the related history table. DatabaseSizeHistory contains the same columns as DatabaseSize, except the SizeMB column is not a computed column in the history table.


When I initially created the table, I typoed the formula in the computed column. You can’t alter a computed column — you must drop and recreate the column. This is no problem, just turn off system versioning and alter your table, and turn system versioning back on.

But if you try this without specifying your history table, you will find that it stops using the history table created earlier and makes a new history table.

dbo.DatabaseSize is a system versioned table. The history table now shows as dbo.MSSL_TemporalHistoryFor_1909581841

If you specify your history table while turning system versioning back on, you will encounter an error:

Setting SYSTEM_VERSIONING to ON failed because column 'SizeMB' at ordinal 5 in history table 'Test.dbo.DatabaseSizeHistory' has a different name than the column 'ValidFrom' at the same ordinal in table 'Test.dbo.databasesize'.

Temporal tables match the columns between the current table and history table not only by name and data type but by the column’s ordinal position. Dropping and adding the computed column changed its order as it was added to the end of the table.

You can change the column order of a table in the SQL Server Management Studio UI by right-clicking on the table, selecting Design, and then dragging the column to the correct position. Note that you cannot do this on the system-versioned table while system versioning is on. You can either change the column order on the history table, or turn system versioning off and then change the current table.

dragging the SizeMB column to the bottom of the columns list in the table.

Once the column orders match, you can turn system versioning back on and specify the the history table.

ALTER TABLE [dbo].[DatabaseSize]
SET (SYSTEM_VERSIONING = ON (HISTORY_TABLE = [dbo].[DatabaseSizeHistory]));

This time, the command should complete successfully. You’ll want to drop any unused auto-created history tables before you’re finished.

Contact the Author | Contact DCAC

SQL Server Replication and AlwaysOn Availability Groups

Published On: 2021-04-12By:

Using SQL Server Replication with AlwaysOn Availability Groups is a pretty straightforward process at this point. Having the publisher be a member of an Availability Group has been supported for years now. You can however run into trouble when trying to create a new replication publication on a server that isn’t the server that you were using as the Primary server when you set up the first publication. When using a different server in the availability group you’ll get an error back from SQL Server Management Studio which says “Could not find server {old primary server} in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. Error 7202”.

Let me explain what is happening, and how to work around it.

sql1a – Server that was the active replica when the initial publication was setup

sql1b – server that is now the active replica

If you try to set up a new publication on sql1b, you’ll get the error message that is described above. If you write out the replication commands manually you won’t get this error. This error only happens within the GUI.

The easy solution is to fail the Availability Group back to sql1a and create the publication. But what if that isn’t an option because that server no longer exists? The easy solution here is to create a linked server on all the servers in the AG, using the name of the server that was used to set up replication initially, in this case, sql1a. I then configure this linked server to point to the Availability Group listener name. So that way the linked servers, on any server, will always point to the active server. If you are setting up replication you are on the active server already, so the linked server just points back to itself.

By setting up a linked server with this name, that points back to the listener this allows replication publications to be created which sql1b is the active replica within the Availability Group.

It’s a quick and easy fix that’ll get you past the error message that SQL Server Management Studio is throwing.

Denny

Contact the Author | Contact DCAC
1 2 3 488

Video

Globally Recognized Expertise

As Microsoft MVP’s and Partners as well as VMware experts, we are summoned by companies all over the world to fine-tune and problem-solve the most difficult architecture, infrastructure and network challenges.

And sometimes we’re asked to share what we did, at events like Microsoft’s PASS Summit 2015.

Awards & Certifications

Microsoft Partner   Denny Cherry & Associates Consulting LLC BBB Business Review    Microsoft MVP    Microsoft Certified Master VMWare vExpert
American Business Award 2021 Gold    American Business Award 2021 Bronze    FT Americas’ Fastest Growing Companies 2021   INC 5000 Award for 2020    American Business Awards People's Choice    American Business Awards Gold Award    American Business Awards Silver Award
FT Americas’ Fastest Growing Companies 2020       Best Full-Service Cloud Technology Consulting Company       Insights Sccess Award    Technology Headlines Award
Share via
Copy link