New answers tagged server
There are several reasons why this can happen: Make sure you are not using the query cache on your old server and not on the new one. Execute always benchmarks with SELECT SQL_NO_CACHE. Execute the same queries several times. If it is a new server -the buffer pool, filesystem cache and other buffer are probably not yet settled for best performance, ...
I would say you don't need all the start events, just the completed. I don't see that you are capturing data just for the SCOM database either. Extended events can cause an overhead just near to what SQL Server traces will depending on what you are trying to capture. You are basically capturing every query that comes across the server and telling it to wait ...
I wrote a series on SQLServerCentral about baselines that might be of interest to you: http://www.sqlservercentral.com/Authors/Articles/Erin_Stellato/351331/ And as Shawn so kindly mentioned, I also have a Pluralsight course. If you have more questions, feel free to contact me (erin at sqlskills dot com). Erin
Troubleshooting Performance It is all about the queries. You need only three bits of information about your queries: CPU, Duration & Reads. SELECT TOP 50 qs.creation_time , qs.execution_count , qs.total_worker_time as cpu , qs.total_elapsed_time as duration , qs.total_logical_reads as reads , t.[text] FROM sys.dm_exec_query_stats qs CROSS APPLY ...
You cannot insert a row without specifying values for columns that have NOT NULL constraints. What would be the point of having NOT NULL constraints on those columns if it wasn't enforced? You would need to remove the NOT NULL constraint clause for each column in the table in order to insert a row that only contains the Zip code value. This begs the ...
Nope, you'll need to provide values for the columns which are listed as NOT NULL.
@Kin yes he wants just to remove the partition so it becomes non- partitioned table. as Aaron said I would select * into new_table from old_paritioned and rename the new table and drop the partitioned table.I am sure they are better ways of doing that though. If it is large table(billion of rows) copying all rows takes time and resources.
Sounds like PhpPgAdmin is probably doing a session-level SET bytea_output = 'escape'. If you open a new psql session and SHOW bytea_output; it'll be hex there. PhpPgAdmin may offer a way to control this behaviour, or it might be hard-coded to work around compatibility issues (if it doesn't understand the hex format for bytea).
There is no way to do that by changing a server parameter. NULL is different from an empty string so there is no reason to have that. You could change your application to send NULL to your SQL statement or add a condition to your query. INSERT INTO table (column1) values (IF(LENGTH('$variable')=0,NULL,'$variable'));
Top 50 recent answers are included