|
I've had a similar issue with August 2017 update; but this was with Lenovo's sound card drivers.
I installed Windows 10 Fall Update on last week end, and happily did not encounter any issue (yet).
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
|
I guess just loading a bad NVidia Open CL driver like last time wasn't enough of a gotcha. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
once upon a time nads hinted at turning w10 into a service,
and every w10 update has had major issues (way more than any previous versions' updates ever)
it's not the haters - this is being reported in the press: ms are killing themselves
tell me, how are ms going write a SLA for that?
and ffs, how can they with a straight face ask businesses to adopt 10?
Installing Signature...
Do not switch off your computer.
|
|
|
|
|
Reading about these issues, I think I'll wait. Installed it on a VM of mine (guinea pig), but how does MS expect us to survive the more frequent releases?
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I found we use SQL triggers a bit too much...
336 triggers on 1450 tables... (~23%)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
We hardly use triggers at all. Interesting that you have more than 5.
|
|
|
|
|
0 triggers on 0 tables (NaN%)
|
|
|
|
|
Isn't it 100%? 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Yes but it's also 42%, and 9001%, etc..
|
|
|
|
|
You obviously need one table per trigger to keep track of them. Then add a trigger for each table if any trigger changes. FTFY.
... such stuff as dreams are made on
|
|
|
|
|
Actually some of the triggers are there to log data changes (on important tables)...
Others are for data integrity...
And others are for sync with externals...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'd start looking for a new job before the house of cards falls down.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: (~23%)
We got you beat. 247 triggers on 741 tables, exactly 1/3, although not intentional.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I avoid them as triggers too easily lend themselves to database-vendor specific code.
Installing Signature...
Do not switch off your computer.
|
|
|
|
|
My former bosses have about 10 - 15 triggers on each and every table, some of them thousands of lines long. A nightmare.
Especially after that experience: 0.0 triggers per table and not a single trigger more.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
That sounds awful... Our triggers are short (sometimes 2-3 triggers on the same event, just because they all do something else)...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
The major part of the application logic took place in those triggers. Guess why I run out of job interviews when I hear 'Access' or ' Former Acess project that has ben ported to xxx'.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Hey! I'm (still) working on an Access project ported to SQL Server. Don't knock it if you haven't tried it!
Triggers are useful, but to embed business logic? Then even I would run away...
8)
|
|
|
|
|
It's the 'We don't need any architecture or documentation, and you are a fool for asking.' mentality that I don't like. They can keep on doing their stuff as long as they like (or until their customers finally have enough), but I will not work like that again.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Oh, indeed! Fortunately this project was written originally (entirely in Access) by someone who actually had a clue, and the 'owner' who understands the business (and is also a dev) has worked on it - so I have been able to gradually document the entire setup, what things represent and do etc.
Whilst it's still very much a work in progress, I've been able to add all sorts of functionality, but I've discovered nearly 60 GOTCHAs (so far!) when moving from Jet to SQL - documented hereabouts somewhere. The trickiest new feature was CRM functionality as the data had to be imported from another (commercial) system where ALL information (used in tens, if hundreds) of different views was all stored in ONE huge SQL table and extracted by the most complicated series of inner joins and table aliases that I have ever seen. The person who wrote that must have been on acid! "Normalisation - never heard of it!" Definitely write only code...
|
|
|
|
|
Sounds like a bunch of trigger happy bosses 
... such stuff as dreams are made on
|
|
|
|
|
CodeWraith wrote: My former bosses
Database guys in charge of application development? Sounds like it to me.
|
|
|
|
|
Even worse. Access guys in charge. I must have offended him when I looked at that stuff and asked him what this particular form of insanity is called.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Lotta time I see...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Working on a review of the DB design to suggest improvements...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
