What I noticed did work is installing a new SQL server and instance, but trying to restore a db backup used in a different instance already installed on system, makes the restore process fail every time with an error saying it cannot find the instance location.
So you would literally have to make a new db and connect samba that way. But no one wants to redo everything they worked so hard on all over again. Thus as previously suggested by a member here
Allow system restore points, so at least you can restore to previous times in case something like this happens, otherwise you may end up having to reset entire PC on win 10
I see a lot of discussion about it and most of them involve 2014 and 2008 versions. Has anyone here experienced it with recently released 2016 version?
I just recently actually installed sql 2016, and to my surprise!!! sql service started again?! and I had access to my database in 2014ā¦ So weird. I think the win 10 sql update mustve triggered the sql service start file to corrupt, and 2016 may have fixed itā¦
I have not seen the problem either. And both my Prod systems run SQL 2014, Win 10 and get updates. Still, this scares the shit out of me. I canāt have them go down due to some corrupted MS update bullshit.
It is not. Been there since Win 7.
Well, there be the deciding factor to upgrade my systems from 2014.
I hace a intel core i7 notebook, NEW, brand NEW, fresh install, the only think running there is an antivirus AVG (latest install), samba and SQL 2014.
I had this problem, service sometimes not starting FOREVER. not even MS knows whats wrongā¦ I have a friend here in NATAL, taht works in MS labā¦ he had this notebook for two daysā¦
The bottom lineā¦ its MICROSOFTā¦ it can failā¦
sometimes it boot up the notebook and service starts without problemsā¦ 1 or 2 out of 10 service does not start, it does not failā¦ it does simply not start.
I iupgraded to 2016ā¦ seems that problems are less frequentā¦ sometimes, very rarely, but sometimes service does not startā¦
I did happen to me yesterday. SQL Agent start then stop. Tried many things suggested online nothing work. I have to restore to before windows 10 latest update. Update really screw up workgroup/home group. After estate every thing work fine.
We should just make sure from now on to have system restore points setup for win10 and continuous backups just in case something like this occurs. I have a feeling itās going to happen often with older versions of sql. Possibly good to advise all samba users about this conflict so people are aware just in case they are affected also
