then its time for you to read the manuals - keyword TRIM

based on the code by Jeff the only way you get that error is if your file contains a line that has data and does not have a ":" or...

It is normal on the case of that table - it is a very small table and even if you rebuild it manually the fragmentation may not change - or...

you really have no idea of what you are doing neither do you follow the advise of this forum experts. on this case you decided to change the supplied code...

on some of my busy and misbehaved servers I have the following query running every 10 seconds with output to a table.

with this table its easy to identify queries that...

I would add to that a verification - if number of posts = number of spam posts and user has more than 5/10 such posts just block them next time...

a simple google search finds a few hits.

one of them is https://dba.stackexchange.com/questions/41961/how-to-find-all-positions-of-a-string-within-another-string

have a look at the following links for info

https://www.sqlservercentral.com/forums/topic/review-ola-hallengren-indexoptimize-parameters

https://www.youtube.com/watch?v=rvZwMNJxqVo

https://www.sqlservercentral.com/forums/topic/index-fragmentation-42

regarding your particular need to do it on a subset of tables - don't worry about creating a custom script for it.

Ola's...

• This reply was modified 4 years, 2 months ago by frederico_fonseca.

IF (SUSER_NAME() in ( 'DOMANINA\GMSA_999SQLAgt$', 'user', 'user3', 'user4'))

this is basic sql

having one of the above running you always have the statements on the database for investigation.

Even if they aren't consuming high CPU having the history (mainly the second query I...

I could not find it (and I'm sure you searched as well) - but you can do it manually with T-SQL.

what the wizard does on the background is defined in...

you don't do it when you have high cpu - you have it running all the time with 10,20, 30, 60 seconds interval or so depending on how busy your...

I'll let Jeff do some chopping but WHY Reorganize? this should be avoided almost at all costs (very few exceptions)

with db in simple recovery the following can cause the log to grow.

• Replication
• CDC
• Large size updates (or medium size parallel updates) / same for Deletes
• big indexes being...

the OP means the pipe "|" between strings