User Tools

Site Tools


windows:sqlserver

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
windows:sqlserver [2015/01/14 03:57] – [backup and restore bak file] adminwindows:sqlserver [2022/10/29 16:15] (current) – external edit 127.0.0.1
Line 26: Line 26:
 </code> </code>
   * Step2: Using SQL Server Configuration Tool, go to **SQL Server Network Configuration**->**Protocols for MSSQLServer**->**TCP/IP**{{:windows:sqlserver-ipconfig.png|}}   * Step2: Using SQL Server Configuration Tool, go to **SQL Server Network Configuration**->**Protocols for MSSQLServer**->**TCP/IP**{{:windows:sqlserver-ipconfig.png|}}
 +==== view database config(data config, log config...) ====
 +  * step1: select database as below image:
 +{{:windows:database-config.png|}}
 +  * step2: right-click the database and click **properties** to see the database settings as below image:
 +{{:windows:database-setting.png|}}
 ==== reset password ==== ==== reset password ====
 ===== Backup and restore ===== ===== Backup and restore =====
 ==== backup and restore bak file ==== ==== backup and restore bak file ====
-  to restore: right click **databases** and select restore database +  to restore: right click **databases** and select restore database 
-  to backup:  right click **database name** and select **tasks -> backup**+  to backup:  right click **database name** and select **tasks -> backup**
 ==== backup and restore sql scripts ==== ==== backup and restore sql scripts ====
 +  * backup: right click **database name** and select **tasks->generate scripts**
 +==== attach database file(mdf file) ====
 +===== debug in sql server =====
 +==== query log in sql server ====
 +  * to view query log in sql server, we use sql server profiler
 +  * with sql server express, we use expressprofiler(because in this version, the sql server profiler not exists): https://expressprofiler.codeplex.com/
 +==== The actual stored procedure line number from an error message ====
 +Error line numbers may not match the number returned in the error always, this is because when **the SQL server executes a stored proc, it has its own compilation & execution methodology**, so the line numbers vary based on the execution order it takes
 +==== Debug stored procedure with break point ====
windows/sqlserver.1421207830.txt.gz · Last modified: 2022/10/29 16:15 (external edit)