chore: sql server rename column

Author: tianzhou

content/reference/sqlserver/how-to/_layout.md

@@ -0,0 +1,6 @@
+---
+---
+
+## [Overview](/reference/sqlserver/how-to/overview)
+
+## [How to RENAME column](/reference/sqlserver/how-to/how-to-rename-column-sqlserver)

content/reference/sqlserver/how-to/how-to-rename-column-sqlserver.md

@@ -0,0 +1,83 @@
+---
+title: How to RENAME a column in SQL Server
+---
+
+_Official documentation: [Rename columns](https://learn.microsoft.com/en-us/sql/relational-databases/tables/rename-columns-database-engine)_
+
+## Basic Syntax
+
+The `COLUMN` parameter is required to specify that you're renaming a column rather than another database object.
+
+```sql
+EXEC sp_rename 'Schema.TableName.OldColumnName', 'NewColumnName', 'COLUMN';
+```
+
+## Managing Dependencies
+
+When renaming columns, it's critical to identify and update all dependencies to prevent application failures.
+
+### Identifying Dependencies
+
+Use `sys.sql_expression_dependencies` to find objects that reference the column:
+
+```sql
+SELECT
+    OBJECT_SCHEMA_NAME(sed.referencing_id) AS ReferencingSchema,
+    OBJECT_NAME(sed.referencing_id) AS ReferencingObject,
+    o.type_desc AS ObjectType
+FROM sys.sql_expression_dependencies sed
+JOIN sys.objects o ON sed.referencing_id = o.object_id
+WHERE
+    sed.referenced_id = OBJECT_ID('dbo.Customers')
+    AND sed.referenced_minor_id = (
+        SELECT column_id
+        FROM sys.columns
+        WHERE object_id = OBJECT_ID('dbo.Customers')
+        AND name = 'CustomerPhone'
+    );
+```
+
+### Updating Dependencies
+
+After renaming columns, dependent views and stored modules may still reference the metadata of the old column name. SQL Server provides system stored procedures `sp_refreshview` and `sp_refreshsqlmodule` to refresh these references:
+
+```sql
+-- Refresh a specific view after column renaming
+EXEC sp_refreshview 'dbo.CustomerContactList';
+
+-- Refresh a stored procedure, function, trigger, or view
+EXEC sp_refreshsqlmodule 'dbo.GetCustomerDetails';
+```
+
+- `sp_refreshview`: Specifically for views that have become invalid after column renaming
+- `sp_refreshsqlmodule`: Works on multiple object types (stored procedures, functions, triggers, and views)
+
+Limitations:
+
+- They work only if the column name changes don't break the logic (same column order and data types)
+- Text-based dynamic SQL references in the object code still need manual updates
+
+## Schema Binding
+
+For schema-bound objects (views, functions), you must:
+
+1. Drop the schema binding first
+1. Rename the column
+1. Recreate the schema binding
+
+```sql
+-- 1. Drop the schema-bound view
+DROP VIEW dbo.CustomerDetailsView;
+
+-- 2. Rename the column
+EXEC sp_rename 'dbo.Customers.CustomerPhone', 'ContactNumber', 'COLUMN';
+
+-- 3. Recreate the view with schema binding
+CREATE VIEW dbo.CustomerDetailsView
+WITH SCHEMABINDING
+AS
+    SELECT CustomerID, CustomerName, ContactNumber
+    FROM dbo.Customers;
+```
+
+Note that `sp_refreshview` and `sp_refreshsqlmodule` cannot be used with schema-bound objects, as these objects require explicit recreation after column changes.

content/reference/sqlserver/how-to/overview.md

@@ -0,0 +1,5 @@
+---
+title: 'SQL Server How-to Guide'
+---
+
+This page lists the common SQL Server how-to guides.

src/app/[locale]/reference/sqlserver/how-to/[...slug]/page.tsx

@@ -0,0 +1,33 @@
+import Route from '@/lib/route';
+import {
+  generatePostStaticParams,
+  generatePostMetadata,
+  default as DocPage,
+} from '@/components/pages/docs/docPage';
+
+const DIR_PATH = `${process.cwd()}/content/reference/sqlserver/how-to`;
+const FILE_ORIGIN_PATH =
+  'https://github.com/bytebase/bytebase.com/tree/main/content/reference/sqlserver/how-to';
+
+export function generateStaticParams() {
+  return generatePostStaticParams(DIR_PATH);
+}
+
+export default function Page({ params }: { params: { slug: string[] } }) {
+  return (
+    <DocPage
+      params={params}
+      dirPath={DIR_PATH}
+      fileOriginPath={FILE_ORIGIN_PATH}
+      routePath={Route.REFERENCE_SQLSERVER_HOW_TO}
+    />
+  );
+}
+
+export async function generateMetadata({ params }: { params: { slug: string[] } }) {
+  return generatePostMetadata({
+    params,
+    dirPath: DIR_PATH,
+    routePath: Route.REFERENCE_SQLSERVER_HOW_TO,
+  });
+}

src/app/[locale]/reference/sqlserver/how-to/layout.tsx

@@ -0,0 +1,11 @@
+import DocsLayout from '@/components/pages/docs/layout';
+
+const DIR_PATH = `${process.cwd()}/content/reference/sqlserver/how-to`;
+
+export default function DocLayout({ children }: { children: React.ReactNode }) {
+  return (
+    <DocsLayout dirPath={DIR_PATH} includeSearch={false}>
+      {children}
+    </DocsLayout>
+  );
+}

src/app/[locale]/resources/page.tsx

@@ -33,6 +33,10 @@ export default function ResourcesPage() {
           />
           <ResourceCard title="🐬 MySQL How-to Guide" link="/reference/mysql/how-to/overview" />
           <ResourceCard title="🐬 MySQL Error Reference" link="/reference/mysql/error/overview" />
+          <ResourceCard
+            title="🛢️ SQL Server How-to Guide"
+            link="/reference/sqlserver/how-to/overview"
+          />
           <ResourceCard
             title="🏠 ClickHouse How-to Guide"
             link="/reference/clickhouse/how-to/overview"

src/lib/route.ts

@@ -83,6 +83,7 @@ const Route = {
   // reference
   REFERENCE_POSTGRES_ERROR: '/reference/postgres/error',
   REFERENCE_POSTGRES_HOW_TO: '/reference/postgres/how-to',
+  REFERENCE_SQLSERVER_HOW_TO: '/reference/sqlserver/how-to',
   REFERENCE_CLICKHOUSE_HOW_TO: '/reference/clickhouse/how-to',
   REFERENCE_MYSQL_ERROR: '/reference/mysql/error',
   REFERENCE_MYSQL_HOW_TO: '/reference/mysql/how-to',