Is"always" a workable term to describe the uptime of a server? [closed] - requirements

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
since me and my colleagues had a discussion about this, I wanted to ask, if you would use the term "always" to describe the uptime of a server in a requirement.
Example:
The server should be always reachable.
Since, in my opinion, alsways can't be measured, I would rather write the requirement like this:
The uptime of the Server should be >= 99%.
Thanks in advance!

Do not use always, it isn't possible to achieve. Uptime is discussed in terms of nines: https://en.wikipedia.org/wiki/High_availability#%22Nines%22
Amazon S3 for example, offers 4 nines of availability (99.99%).
Look at: https://uptime.is/ to fully understand how much downtime you are allowed for a given sla.

Related

Suggested format for SQL statement [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I've always struggled with how to format SQL queries in terms of whitespace, alignment, etc. It seems whenever there is an "auto-formatter" it seems to format things differently than the next one, whether it is within a SQL client or a website or text-editor that does various language formatting. Are there any guideline(s) for how SQL should be formatted for best readability? Here is an example of how I currently do it:
SELECT
name
FROM
sales_instance si
JOIN main_iteminstance i ON si.instance_id=i.id
ORDER BY
name
Also, yes I know this may be 'opinion-based' and people may want to close it for that, but I think this answer is helpful as to writing clean SQL and hopefully someone can provide a good summary of the available formats or guidelines.

Can I use shared hosting for dynamic website? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Can anyone help me
We'd like to create our startup MVP dynamic website with transaction, scheduling(calendar) and matching system using Python(django) and mongodb, can we use a shared hosting for that? (if yes, can you guys recommend?) reason is that no one in our team knows linux yet if we use vps.
beginner here and we don't have tech lead yet in our team 😣 we're trying to do it on our own (funding reasons).
We believe in our idea but we're short in resources. I hope you guys can help us. Thank you in advance!

what to expect from a face to face Data science interview, after taking an online aptitude test and an assignment [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I don't know if this is the right place to ask this question, I applied for a data science job, I was given an aptitude test to complete and a data science question to solve, so three days ago, I was told to make myself available for a face to face interview. now am kind of confused I don't know what else to expect during the interview. any help, please.
Expect to be asked some basic domain questions
you be might be asked on my you choose this career path
if you have been giving an assignment you might be asked to explain it
they might test your soft skills

Meaning of "Query From Hell" [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm reading Scaling Out SQL Server and came across with this in the article. I googled it and not enough answers. Can anyone enlighten me?
CPU bound query.
A SQL Server instance can process a single query for hours without any effect on the whole system, because there are still 7 other SQL Server instances free to process other queries.
This is not true for IO bound query, since the 8 SQL Server instances are using a shared disk.
From the preceding sentence in that article:
a query that ties up all the database resources for hours.

Differences between SAS and SQL [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Can anyone articulate what the key differences are between SAS and SQL? I haven't worked much with SAS but went on a weeks training course, and basically it seemed like the equivalent but more convoluted and was able to do graphs.
Would appreciate some key bullet differences between them.
Standard SQL is a language to query, manipulate and define data in any(!) database. It is like the "latin language" of DB systems. Everyone knows it in order to perform standard tasks. SAS is like an extension to that with many functions.
I found a good document:
http://www.sascommunity.org/mwiki/images/5/52/CMSSUG-0506-SQL.pdf