General |
- SQL Server 2008 R2 Pricing
- Microsoft SQL Server 2008 R2 Download and Support
- Microsoft SQL Server 2005 Home
- Feature Pack for Microsoft SQL Server 2005 – February 2007
- How to identify your SQL Server version and edition
SQL Server 2008 RTM 10.0.1600 SQL Server 2008 SP1 10.0.2531 SQL Server 2005 RTM 9.0.1399 SQL Server 2005 SP1 9.0.2047 SQL Server 2005 SP2 9.0.3042 SQL Server 2005 SP3 9.0.4035 SQL Server 2000 RTM 2000.80.194.0 SQL Server 2000 SP1 2000.80.384.0 SQL Server 2000 SP2 2000.80.534.0 SQL Server 2000 SP3 2000.80.760.0 SQL Server 2000 SP3a 2000.80.760.0 SQL Server 2000 SP4 2000.8.00.2039
- MSDE 2000 Release A
Free version of SQL Server 2000 Desktop Engine - Finding and Fixing Slammer Vulnerabilities
SQL Server Express 2005 |
- Microsoft SQL Server Express 2005 brief introduction
- Download SQL Server Express
- Error “Performance Monitor Counter Requirement" when installing SQL 2005 Express SP2Product: Microsoft SQL Server 2005 Express Edition — Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The configuration registry key is invalid.
- Make sure the Last Counter and Last Help values are in-sync
- Try to run: lodctr /R:PerfStringBackup.INI to restore the backup copy of the Performance Counter Names list
Maybe due to an old SQL Server setup added some counter names remain at performance counter that corrupt the newer setup process
MSDE 2000 |
- Login CLI with current user: osql -E
- How to manage the SQL Server Desktop Engine (MSDE 2000) or SQL Server 2005 Express Edition by using the osql utility
- Check existing db: SELECT name, filename FROM sysdatabases
- Backup db: BACKUP DATABASE dbname TO DISK = ‘c:\backup\dbname.bak’
- Restore db: RESTORE DATABASE dbname FROM DISK = ‘c:\backup\dbname.bak’
Need the database not active, else: Exclusive access could not be obtained because the database is in use. - Remove all users to the db: ALTER DATABASE dbname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
User Instances |
- MSDN: Working with User Instances
- Enable when install, or run:
exec sp_configure 'user instances enabled', 1 Reconfigure
BCP Utility |
- SQL Server數據導入導出工具BCP詳解
- If Format file defined wide character data but import data is normal character, then will have error: Error = [Microsoft][SQL Server Native Client 10.0]Unexpected EOF encountered in BCP data-file
Sample Database |
Reporting Services |
General
Development
- Dynamic Connection Strings in Reporting Services 2005
- MSDN Forums thread on Dynamic data source name
Reporting Services Tutorials |
Mirroring (After SQL2005) |
- TechNet: SQL Server Mirroring
- SQL2008: Synchronous Database Mirroring (High-Safety Mode)
- Setup Database Mirroring without join into a domain
- Use certificates for servers authentication
Will have problem of certificate created with an invalid date value - Detail CLI config of database mirroring in SQL 2005 (same domain)
- Another example of connecting two standalone SQL Server 2005 DB in a mirroring setup
- SQL Server 2005 Encryption – Certificates 101
- Use certificates for servers authentication
- SQL SERVER – Database Mirroring. Error: 1475, Error: 1478, Error: 1412.
At the Mirror server, need to restore a Full backup as well as a Log backup with NO RECOVERY option - Manual Failover Mirrored Database at a Standby Server
- ALTER DATABASE [dbname] SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS
- SQL2008: Forced Service (with Possible Data Loss)
- SQL2005: Forced Service (with Possible Data Loss)
- SQL2008: Prerequisites, Restrictions, and Recommendations for Database Mirroring
Howto |
- Transaction Log Explained
- sqlskills.com: BACKUP LOG WITH NO_LOG – use, abuse, and undocumented trace flags to stop it (Obsolete command for SQL 2008)
- Install SQL Server 2000 before SP2 to Windows Server 2003
- Ignore the warning, install SQL Server database engine / analysis service first
- Required to setup strong password in SQL Server SP3:
- Shrink a database to reduce database file size
- MSDN: SQL 2016 – Shrink a Database
- Use the SQL statement, it will try to reduce the database size to 10% of the file size.
# the first line disable transaction log, make sure you backup the database before proceed! ALTER DATABASE database_name SET RECOVERY SIMPLE; DBCC SHRINKDATABASE (DatabaseName, 10); ALTER DATABASE database_name SET RECOVERY FULL;
- Use the SQL statement, it will try to reduce the database size to 10% of the file size.
- MSDN: SQL 2016 – Shrink a Database