Microsoft SQL Server - MSSQL / SQLSERVER

• Log into Studio Using the server name - and not localhost or ip address
• Run Through Publisher Wizard

1. Use “Transaction Publication” Publication Type
2. Select Database & Table(s) you want to replicate
3. Create Snapshot
4. Use SQL Server Agent Service Account for Snapshot agent. SQLSERVERAGENT neeeds file access to the MSSQL\repldata folder.
5. Enter Publisher Name - “gor_test”

This creates “distribution” mdf and ldf files in the MSSQL\DATA folder.

1. Create database - but NOT any tables.
2. I using the Push approch (pushed from Pubisher to Subscriber) - all config done on Publisher.
3. Needed to add SQLSERVERAGENT with read / write access to the repldata folder
4. Create a SQL user on the Subscriber with owners rights to the specific database.
5. On the PUBLISHER in Subscriber Properties set this as the Subscriber Connection

• You can add a new column at the end of your existing table
• You cannot change the type of an existing Column - “unable to modify table - cannot drop the table 'dbo.myTable' because it is been used for replication
• you cannot rename a column - because “it is published for replication”
• You cannot add a new column and move it between two existing columns - as this needs to drop the table.

• Stop Replication (Right Click - View Sync Status)
• Remove Table from Article
• Make the changes on Publisher which require the table to be doped and re-inserted.
• Add table back into Article
• Right Click Publisher and Reinitialize All Subscribers - select “Use a New snapshot / Generate the new snapshot now” - Mark for Re-initialization

• Making Schema Changes on Publisher

• http://www.simple-talk.com/sql/database-administration/creating-csv-files-using-bcp-and-stored-procedures/
• http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/2fd020c9-4cc9-4f76-8fc8-d91383c85782/

• http://www.howtogeek.com/50295/backup-your-sql-server-database-from-the-command-line/

This allows you to restore the master database, and also add the windows local administrator to add user with whatever rights necessary. e.g. sysadmin for local admin

• Stop SQL Service
• Start command window 'run as an administrator'.
• Change to the the required Folder for sqlservr.exe , e.g. C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn
• Run below command

"sqlservr.exe -c -m"

• https://technet.microsoft.com/en-us/library/ms165662(v=sql.90).aspx
  

select @@servername
go

select @@version
go

select serverproperty('edition')
go

Reference: https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-configure-transact-sql?view=sql-server-ver15

sp_configure;

When executed with no parameters, sp_configure returns a result set with five columns and orders the options alphabetically in ascending order, as shown example out[ut.

Note, when you run the sp_configure command by default you only get to see the standard configurations options

If you want to see the Advanced options as well you need to run the following command:

sp_configure 'show advanced options', '1';
RECONFIGURE

And THEN run the command (advanced example output below):

sp_configure

Caution!
When the option Show Advanced Options is set to 1, this setting applies to all users. It is recommended to only use this state temporarily and switch back to 0 when done with the task that required viewing the advanced options.

The below details gives an example on how to enables advanced options, disables the Database Mail XPs and then re-disables the advanced options again.

EXECUTE sp_configure 'show advanced options', 1;
RECONFIGURE;
EXECUTE sp_configure 'Database Mail XPs', 0;
RECONFIGURE;
GO
EXECUTE sp_configure 'show advanced options', 0;
RECONFIGURE;

Options that require SQL Server to restart will initially show the changed value only in the value column. After restart, the new value will appear in both the value column and the value_in_use column.

If the SQL database has large transactions logs - when a SQL server restarts the Database can go into recovery mode for an extended period of time.

dbcc sqlperf(logspace)

checkpoint

You usually need to run this command more than once. After it completes run the dbcc sqlperf(logspace) again to confirm. After running this twice it the transaction log space used for the database should be < 1%.

Once the transaction space has been reduced - you should be able to shrink the Transaction log file to reduce space used on the Server. To do this run the shrink command and you can set the file size you want to shrink the Transaction log file to. You can use the GUI . Select the database → Right Click → Task → Shrink → Files Select File Type → Logs Select “Reorganize pages before releasing unused space - Shrink file to: ” and enter the file size.

To view the command line that the above GUI would run, select (at the top of the page)
Script → Script Action to New Window

This should give an output similar to below:

USE [eGMasterDB]
GO
DBCC SHRINKFILE (N'eGMasterDB_LOG_Device' , 2048)
GO