Re: Don't use databases
Posted: Sat Nov 24, 2018 12:05 pm
Setting integrated security to false makes it worse for now it asks for username and password. I hate usernames and passwords
With sql server object inspector I can only view these properties like maximum memory but can't change them for they are disabled (greyed out)Dann Corbit wrote: ↑Fri Nov 09, 2018 9:54 pmSQL Server (when installed with defaults) makes lots of assumptions about resources that are not necessarily valid.Henk wrote: ↑Fri Nov 09, 2018 3:34 pm "Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was "
I had to wait at least five minutes before data connection to database could be used.
Maybe because my computer was too busy.
Why don't they give a warning if you want to install SQL server on a slow computer.
I don't know what is going on.
Might be windows 10 secret services being overly busy. I don't know.
Or maybe this database contains too many chess positions? Makes no sense too.
One of them is "all your resources are belong to us!", since the SS team is probably run by aliens.
SQL Server will use all the available memory. Then when you run some other task that consumes a lot of memory, you have paging madness.
So limit SQL Server to a sensible amount of memory (under: server properties/memory/maximum memory). Also, don't install SS on a wimpy machine unless you want wimpy data access.
The suggestion of using an embedded database like SQLite is a good one. An embedded database tends to be quite fast, but the down side is it is normally limited to a single user. If that is OK for your application, it is often a good idea.
Once you get used to doing database access, you will never want to go back to files.
Of course I meant sql management studio. At least not fool proof for I don't know how to change maximum memory.Henk wrote: ↑Sat Nov 24, 2018 12:35 pmWith sql server object inspector I can only view these properties like maximum memory but can't change them for they are disabled (greyed out)Dann Corbit wrote: ↑Fri Nov 09, 2018 9:54 pmSQL Server (when installed with defaults) makes lots of assumptions about resources that are not necessarily valid.Henk wrote: ↑Fri Nov 09, 2018 3:34 pm "Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was "
I had to wait at least five minutes before data connection to database could be used.
Maybe because my computer was too busy.
Why don't they give a warning if you want to install SQL server on a slow computer.
I don't know what is going on.
Might be windows 10 secret services being overly busy. I don't know.
Or maybe this database contains too many chess positions? Makes no sense too.
One of them is "all your resources are belong to us!", since the SS team is probably run by aliens.
SQL Server will use all the available memory. Then when you run some other task that consumes a lot of memory, you have paging madness.
So limit SQL Server to a sensible amount of memory (under: server properties/memory/maximum memory). Also, don't install SS on a wimpy machine unless you want wimpy data access.
The suggestion of using an embedded database like SQLite is a good one. An embedded database tends to be quite fast, but the down side is it is normally limited to a single user. If that is OK for your application, it is often a good idea.
Once you get used to doing database access, you will never want to go back to files.
Same holds for sql memory studio
Visual studio 2017 now using 850MB memory while I'm doing nothing right now. Using two sql server windows nt 64 processes consuming both about 200 MB. I even don't understand why it needs two processes is one not enough?