SQL Server Script to Rebuild/Reorganize Fragmented Indexes When on a database’s table frequently running INSERT, UPDATE or DELETE queries than we can see indexes on the particular table gets fragmented and the SQL query may run slower as they may choose the non-optimal execution plan. Most of the people asking about Does SQL Server rebuild index automatically or any rebuild criteria? But Rebuilding/Reorganize of fragmented Indexes not supported automatically because rebuilding the indexes is expansive operation so be careful to schedule rebuilding via SQL Server Agent. But hare we are adopting an approach to rebuild or Reorganize only the necessary Indexes instead of all index rebuild, As a general recommendation, the index needs to rebuild that gets fragment percentage more than 30% and reorganize the index that has fragment percentage greater than 10% and less than 30%. The below script rebuilding index one by one, so it won’t be an expansive operation on the production database. --- Rebuild/Reorganize Indexes CREATE TABLE #IndexRebuild ( DatabaseName SYSNAME, SchemaName SYSNAME, TableName SYSNAME, IndexName SYSNAME, [Fragmentation%] FLOAT ) INSERT INTO #IndexRebuild SELECT DB_NAME(DB_ID()) AS DatabaseName, ss.name AS SchemaName, OBJECT_NAME (s.object_id) AS TableName, i.name AS IndexName, s.avg_fragmentation_in_percent AS [Fragmentation%] FROM sys.dm_db_index_physical_stats(db_id(),NULL, NULL, NULL, 'SAMPLED') s INNER JOIN sys.indexes i ON s.[object_id] = i.[object_id] AND s.index_id = i.index_id INNER JOIN sys.objects o ON s.object_id = o.object_id INNER JOIN sys.schemas ss ON ss.[schema_id] = o.[schema_id] WHERE s.database_id = DB_ID() AND i.index_id != 0 AND s.record_count > 0 AND o.is_ms_shipped = 0 AND s.avg_fragmentation_in_percent > 10 DECLARE @RebuildSQL NVARCHAR(MAX) SET @RebuildSQL = '' SELECT @RebuildSQL = @RebuildSQL + CASE WHEN [Fragmentation%] > 30 THEN CHAR(10) + 'ALTER INDEX ' + QUOTENAME(IndexName) + ' ON ' + QUOTENAME(SchemaName) + '.' + QUOTENAME(TableName) + ' REBUILD;' WHEN [Fragmentation%] > 10 THEN CHAR(10) + 'ALTER INDEX ' + QUOTENAME(IndexName) + ' ON ' + QUOTENAME(SchemaName) + '.' + QUOTENAME(TableName) + ' REORGANIZE;' END FROM #IndexRebuild WHERE [Fragmentation%] > 10 DECLARE @StartOffset INT DECLARE @Length INT SET @StartOffset = 0 SET @Length = 4000 WHILE (@StartOffset < LEN(@RebuildSQL)) BEGIN PRINT SUBSTRING(@RebuildSQL, @StartOffset, @Length) SET @StartOffset = @StartOffset + @Length END PRINT SUBSTRING(@RebuildSQL, @StartOffset, @Length) EXECUTE sp_executesql @RebuildSQL DROP TABLE #IndexRebuild The scripts will work like a charm, You can create a stored procedure and can call the stored procedure via the SQL Server agent or via windows task scheduler.

PNPM - Starting new project not working as expected

pradeepkumarjse

I'm trying to use a centralised package manager (pnpm) instead of the vanilla npm, because, I like having space on my hard drive. I'm just trying to get the project started and running into difficulty and there is very little online to actually guide me through starting a project with this package manager. Does anyone have experience getting this to work for React/React Native?

Any ideas would be very welcome.

I've tried two different ways of setting this up:

Created a new project with pnpx create-react-app my-app. This just did exactly what npx create-react-app would do, which includes installing over 200MB of modules I've already had on my system a million times over. I've checked the node_modules folder and none of the files are hard links, they are the modules themselves.

Created a new project without helper commands (i.e. touch App.js, index.js, index.html etc.) then pnpm i react... etc. This worked in a fashion, all of the node packages were links to my global store (in ~/), but then when I try pnpm start to get my server going, I get the error: Cannot find module ... /my-project/server.js. I do not have a server.js file, but then again, using regular npm and npx commands, I have never needed one.

I have used pnpm i server to see if I can get it working that way. Nothing. I'm relatively new to React, so I'm sure I've done something ridiculous, however regardless of how junior I am, I followed the official instructions and they haven't worked for me.

pnpm debug file says the following:

{
  "0 debug pnpm:scope": {
    "selected": 1,
    "workspacePrefix": null
  },
  "1 error pnpm": {
    "message": {
      "errno": 1,
      "code": "ELIFECYCLE",
      "pkgid": "my-cv@1.0.0",
      "stage": "start",
      "script": "node server.js",
      "pkgname": "my-cv"
    },
    "err": {
      "name": "Error",
      "message": "my-cv@1.0.0 start: `node server.js`
Exit status 1",
      "code": "ELIFECYCLE",
      "stack": "Error: my-cv@1.0.0 start: `node server.js`
Exit status 1
    at EventEmitter.<anonymous> (/usr/local/lib/node_modules/pnpm/lib/node_modules/@zkochan/npm-lifecycle/index.js:302:16)
    at EventEmitter.emit (events.js:200:13)
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/pnpm/lib/node_modules/@zkochan/npm-lifecycle/lib/spawn.js:55:14)
    at ChildProcess.emit (events.js:200:13)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)"
    }
  }
}

UPDATE: So I've managed to get it to work, I think... I got hold of all of the required packages that are used in npx create-react-app and put them inside package.json before executing pnpm i. However, aside from wondering whether this is possible without going to that amount of trouble, looking at the file structure, in addition to the aliases I have inside the node_modules folder, I seem to have a hidden folder .registry.npmjs.org. This is exactly the same as the one I have in my system root, that I assumed was the central store.

TLDR: It appears that despite pnpm appearing to work (aliases are created inside the node_modules folder), I still have duplicate packages on my system. Can anyone confirm whether this is the case?