Filegroups

External Article

Move all SQL Server indexed views to a new filegroup

  • Article

As databases grow, it often becomes necessary to add new I/O paths to accommodate the growing space. Even without growth that requires this scale, it can still be useful to utilize multiple I/O devices to spread out the load. One way that you can make optimal use of new drives is to add a filegroup to the database and move certain objects (say, all of your indexed views) to the new filegroup.

2013-02-11

3,176 reads

Blogs

Post-quantum key exchange – Insurance policy for your packets

By

AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...

Plan your 2026

By

If you don't have a plan, you'll accomplish it. That's not a good thing.

Another Change

By

Today Redgate announced that we are partnering with Bregal Sagemount, a growth-focused private equity...

Read the latest Blogs

Forums

Where Your Value Separates You from Others

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Where Your Value Separates You...

Fixing the Error

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fixing the Error

T-SQL in SQL Server 2025: Encoding Functions

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Visit the forum

Question of the Day

Fixing the Error

On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:

SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error?

See possible answers