@PaulWhite Microsoft SQL Server Management Studio 13.0.16106.4 Microsoft Analysis Services Client Tools 13.0.1700.441 Microsoft Data Access Components (MDAC) 10.0.14393.0 Operating System 6.3.14393
I think it's a bit like the CX_PACKET issue where everybody started altering the MAX_DOP setting to reduce CX_PACKET waits instead of looking at the global picture.
I'm not saying your servers aren't having issues, but it might boil down to : "Globally tune the server and the underlying hardware, and the issues might just be resolved."
BTW, are your servers running with the trace flag?
I had a theory at some point that the transaction might not be executing any querys for a while (processing application logic inside the transaction) but tests with powershell indicate that I just always get the statement that last ran on the connection
Could you artificially slow down the storage? Like limit the speed on the SAN switch port to say 1GB instead of what you currently have? (Assuming you have a SAN switch infrastructure behind the SQL server). Or the equivalent on a NAS environment.
I'm building a simple ACL system and the datastore is Postgres 9.6 .
Permissions are assigned to groups, which can have subgroups, and people are assigned to groups.
I have a poor performing query responsible for retrieving all permissions related to a user, and I need your help to optimize/rewri...
@JackDouglas No, I mean I found the obvious bias amusing.
Which isn't to say they don't have a point. I don't know enough about the details to say how 'bad' Windows 10 is compared with other modern operating systems (including the likes of iOS and Android).
I didn't spend hours on it - reading all the embedded links in detail, for example - but the collection in Basic mode seems OK to me. And crash dump reporting has always had a risk of including non-essential information as a side effect.
My phone creeps me out at times with the things it 'knows' about me and my habits. I can always stop using it of course.
> “Sometimes when I’m writing JavaScript I want to throw up my hands and say “this is bull****!” but I can never remember what “this” refers to.” — Ben Halpern
i have 2 Really Big sql server Database tables for IOT Project
First TABLE IS Message (rows count 7,423,889,085 rows)
CREATE TABLE [aymax].[Message](
[MessageId] [bigint] IDENTITY(1,1) NOT NULL,
[ObjectId] [int] NOT NULL,
[TimeStamp] [datetime] NOT NULL CONSTRAINT [DF__Message__Time...
I have a column in sql server that I need to select and I can not select but appear to exist. Is it a read only column or some other issue? Hopefully I added enough info here and I changed the name of my column and table to a generic name.
SELECT t.name as TName, c.name AS ColName
FROM sys.col...
How they actually work
You can see how they're actually implemented now using the test suite's expected output.
Some keys to take away from this.
Inserting into a table with an identity column can now OVERRIDING USER VALUE for the identity column which forces a replacement of the conflicting ...
Think I should separate that from the spec question?
Perhaps, a new question, How are Identity Columns implemented in PostgreSQL 10?
I think conceptually they're different. If the serial produces 10, and you want to override the row you have to delete and reinsert. Now you have sugar on the insert to force the insert overriding the identity.
You can have multiple sequences/serials on a table, but only one identity.
And, you can make an identity GENERATE BY ALWAYS so shy of having a special cause that OVERRIDES VALUES you can insert into the identity column.
depends on your intent. if you didn't want to have users inserting into the column, certainly not.
that's a duplicate key violation that happens after the column has been inserted into manually.
I think most users would want the error to happen if/when a user tries to manually insert into it.
I don't think I ever manually insert a value into a serial column. I want to be notified whenever that happens.
@JackDouglas this isn't currently allowed for serial, CREATE TABLE f ( a serial PRIMARY KEY, b text ); INSERT INTO f (a,b) VALUES (1,'foo'); INSERT INTO f (a,b) VALUES (1, 'bar');
it is allowed for identity columns with OVERRIDING USER VALUE
In the WHERE clause of a SQL query I would expect these two conditions to have the same behavior:
NOT (a=1 AND b=1)
vs
a<>1 AND b<>1
The first condition behaves as expected, and while I epxect the second condition to do the same thing, it does not.
This is very basic stuff, but ashamedly I...
@McNets It's like the scifi or worldbuilding weirdness I click on when the question looks funny, the rest of the network clicks those links to the dba question thinking the same "WTF"
Trying to run an update, but I want to step through it as it's quite a bit of data and don't want to blast it all at once.
In oracle it's a bit easier to select the rows I want because you can include it in the WHERE clause, but T-SQL you include it in the select. I'm wanting to write it somethi...
"Using SET ROWCOUNT will not affect DELETE, INSERT, and UPDATE statements in a future release of SQL Server. Avoid using SET ROWCOUNT with DELETE, INSERT, and UPDATE statements in new development work, and plan to modify applications that currently use it."
I think it makes sense. North Korea was never in the game plan. He just wanted to move all of his military equipment, still with dessert paint, into Europe. And, a force fit for invasion is clearly amassing. He thinks he's playing Risk.
PostgreSQL 10
PostgreSQL 10 brings conditionals to psql. This is no longer an issue.
\if :db_to_run_on = 'dev_database'
TRUNCATE the_most_important_table;
\endif
Oh, anything that provides the solution, no matter how short, should be posted as an answer, not a comment. At least in my opinion. @PaulW may have a different opinion...