Home Forums Thread Like Summary - SQL Upgrade issues I'm seeing

Not an exhaustive list. Not in any order.

* Attempting to upgrade to SQL Server 2016 64-bit upgrade on a 32-bit computer. From what I have seen, this situation is the result of a practice using a workstation as a server and that workstation ran Windows 7 32-bit so SQL Server 2012 32-bit was installed. Later, the practice did an in-place upgrade to Windows 10. The practice never new the computer was 32-bit or forgot.

* Attempting to upgrade to SQL Server 2016 without meeting all prerequisites. SQL Server 2012 MUST be at Service Pack 2 to qualify for an upgrade to SQL 2016. Also, certain Windows Updates must be installed. I've run across several practices who are still running vanilla SQL 2012.

* Too many antivirus programs. Having three or four antivirus programs on the AC server sounds fun. Until your upgrade crashes because they are all fighting to scan the same files.

* AC Server not properly maintained or poor choice made for server. Missing updates, junk programs installed, the list goes on. This often happens when a Windows 10 Home computer was upgraded to Windows 10 Pro or was purchased from a Big Box Store like Best Buy. The computer was never cleaned off and no Windows updates were installed or at least not for a while. In one case, the junk on the machine was preventing installation of updates.

* In-place server upgrade performed to Windows Server 2022. SQL Server 2012, at any service pack level, is not compatible with Windows Server 2022. And now there are issues upgrading to SQL Server 2016.

* SQL Server installed on a domain controller. Good luck with that.

JamesNT

Hi everyone,

I have had a bunch of stuff going on, I know I have been MIA from this forum for a while, part of that has been because....well....AC and our server and network have been running really really well. James speaks the truth in his last post, he provided a superb setup for our office at about 1/2 the price a local IT firm quoted, and it is FAST and flawless.

I would recommend his expertise and dedication to anyone needing help or a new installation.

Gene

@JamesNT

I can vouch for James been a valuable resource for AC users for a long, long time. And, I have heard others give good feedback. I can also tell you that $85.00 per hour is a very good price. Must be the AC discount price. And, I am lucky that I do have a server with two VMs already in place. And, AC runs fine on peer-to-peer networks. Boy, that debate kept the board humming for at least six months.

James, in order to help with your offer, there may be many that don't understand how working with IT remotely works. It may be helpful to explain how a good many companies use IT remotely. (I am guessing probably more than local). You may want to touch on:

1. How you remote in using remote software
2. How you can do nearly 99% of the work as if you were onsite (with a little help from the company plugging in ethernet cables and routers, etc.
3. How available are you for emergency tech support?
4. What constitutes emergency support?
5. Do you provide support strictly by the hour or monthly contracts?
6. How you keep track of everything you do when you are setting up and supporting multiple customers? I have seen some IT support who do better keeping track of encryption keys than the company (even though that isn't their job).

My own personal question is when you refer to the Virtual Machine that is the domain controller, does it go unsaid that it contains Active Directory, DNS, DHCP, etc.? I am guessing yes.

The only thing I would mention about the advice as to not put SQL Server on the same server or VM as the DC, there are many that already have only one server with everything installed on one box, and I am sure that comment coming from a SQL Server and IT expert likely scares them or makes them feel less than smart. Just sayin'.

But, definitely James is a very good resource who has helped a lot of us with his knowledge over the years, and I believe it was never to drum up business. Having said that, let the drums begin. .

Thanks.

James has been a valuable voice for me on this board.
I have every reason to believe that I would have been much better off to go with him from the beginnng, but I wanted to support our local guys. Not always the best plan.

Funny thing is, I never heard that SQL server and domain controller should not be on the same machine -- not until this flap about not supporting SQL12, and not even for a month or more after they first annouced the "simple" plug and play upgrade they first rolled out! I don't think their IT guys had any inkling that some people had the SQL and the DC on the same box.

Also, when I moved from a simple peer-to-peer network to an earlier version of Server Express there were a lot of voices on the internet touting it as the cat's pajamas for small practices. It seemed to work fine, then.

When I upgraded to Server 16 and had the local guys set it up, they said nothing about virtualization or putting the SQL server on a different box. I did discover that they had it all set up so they would "maintain the network" for about $1000/ month -- at which time I said thank you very much and just kept it going myself.

My issue with cost is that Medicare, Medicaid and most insurance companies decide how much to pay doctors based on a formula that includes the cost of office overhead -- but the formulas were derived in a pre-IT era, and despite rosy promises, IT has not reduced overhead or increased efficiency in small family practices -- to the contrary it has INCREASED the overhead by quite a lot. Since we can't charge more for the increse in overhead, we just take home less.

I would hire James in a heartbeat if I weren't so close to the end. At this point I am just limping along, 5 months to go!

Thanks to everyone on this board. AC has been interesting and sometimes fun. I pity the poor souls who are under the yoke of EPIC.

Eventually, you will want to uninstall SQL Server 2012 Express, but I would have someone do that for you just to be on the safe side to insure no other instance is connected to it. The reason is that Windows Updates will continue to tell you SQL Server 2012 Standard needs updates.

So, in the end, Koby's way is much simpler.

And, yes, this does increase my post count.

This PC> C:> Program Files>Microsoft SQLServer> should see MSSQL13.AmazingCharts(That is 2016 version listing) right under MSSQL11.AmazingCharts(2012 Version)