Comments on: Silent install / Command line install of SQL Server 2005 Part 3 http://www.haidongji.com/2005/10/21/silent-install-command-line-install-of-sql-server-2005-part-3/ 季庄新闻--Haidong Ji's Blog Wed, 04 Jan 2012 09:32:09 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Haidong Jihttp://www.haidongji.com/2005/10/21/silent-install-command-line-install-of-sql-server-2005-part-3/comment-page-1/#comment-2156 Haidong Ji Sun, 10 Dec 2006 03:17:43 +0000 http://www.haidongji.com/?p=10#comment-2156 Pretty cool CompanyName. Thanks! Pretty cool CompanyName. Thanks!

]]> By: COMPANYNAMEhttp://www.haidongji.com/2005/10/21/silent-install-command-line-install-of-sql-server-2005-part-3/comment-page-1/#comment-2152 COMPANYNAME Sat, 09 Dec 2006 12:39:15 +0000 http://www.haidongji.com/?p=10#comment-2152 [Options] USERNAME=neosource COMPANYNAME=neosource PIDKEY=ABCDE12345FGHIJ67890KLMNO INSTALLSQLDIR=c:\Program Files\Microsoft SQL Server\ INSTALLSQLDATADIR=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data INSTALLOLAPDATADIR="C:\Program Files\Microsoft SQL Server\MSSQL\OLAP\Data" ADDLOCAL=SQL_Engine,SQL_Data_Files,SQL_FullText,Notification_Services,NS_Engine,NS_Client,SQL_DTS,Client_Components,Connectivity,SQL_Tools90,SQL_Profiler90 INSTANCENAME=MSSQLSERVER SQLPASSWORD=r9p5zh SQLAUTOSTART=1 AGTAUTOSTART=0 ASAUTOSTART=1 RSAUTOSTART=1 SECURITYMODE=SQL SAPWD=r9p5zh DISABLENETWORKPROTOCOLS=0 ERRORREPORTING=1 IP=127.0.0.1 GROUP=SHARINGS SQLACCOUNT=sa SQLPASSWORD=r554453 [Options]
USERNAME=neosource
COMPANYNAME=neosource
PIDKEY=ABCDE12345FGHIJ67890KLMNO
INSTALLSQLDIR=c:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

INSTALLOLAPDATADIR=”C:\Program Files\Microsoft SQL Server\MSSQL\OLAP\Data”

ADDLOCAL=SQL_Engine,SQL_Data_Files,SQL_FullText,Notification_Services,NS_Engine,NS_Client,SQL_DTS,Client_Components,Connectivity,SQL_Tools90,SQL_Profiler90

INSTANCENAME=MSSQLSERVER
SQLPASSWORD=r9p5zh
SQLAUTOSTART=1
AGTAUTOSTART=0
ASAUTOSTART=1
RSAUTOSTART=1
SECURITYMODE=SQL
SAPWD=r9p5zh
DISABLENETWORKPROTOCOLS=0
ERRORREPORTING=1
IP=127.0.0.1
GROUP=SHARINGS
SQLACCOUNT=sa
SQLPASSWORD=r554453

]]> By: The Ji Village News » Silent install / Command line install of SQL Server 2005 Part 4http://www.haidongji.com/2005/10/21/silent-install-command-line-install-of-sql-server-2005-part-3/comment-page-1/#comment-74 The Ji Village News » Silent install / Command line install of SQL Server 2005 Part 4 Mon, 06 Feb 2006 03:01:07 +0000 http://www.haidongji.com/?p=10#comment-74 [...] I’ve documented my experients with SQL Server 2005 silent / command line install in 3 previous posts. They all failed. To be fair, I tested it using September CTP, not the finalized RTM release. [...] [...] I’ve documented my experients with SQL Server 2005 silent / command line install in 3 previous posts. They all failed. To be fair, I tested it using September CTP, not the finalized RTM release. [...]

]]> By: The Ji Village News » SQL Server Management Studio Reports — Potential Management and Permission Issueshttp://www.haidongji.com/2005/10/21/silent-install-command-line-install-of-sql-server-2005-part-3/comment-page-1/#comment-2 The Ji Village News » SQL Server Management Studio Reports — Potential Management and Permission Issues Fri, 21 Oct 2005 16:10:32 +0000 http://www.haidongji.com/?p=10#comment-2 [...] To prove my theory, I created a login for AdventureWorks, a replacement for Northwind and Pubs. I gave this login db_reader and db_writer rights, a common practice for a regular user. I then logged into this database with this login, using SSMS. Sure enough, under this regular user’s login, when I clicked on any server reports, I got a permission error. I haven’t checked database status reports yet, because I’ve been playing with silent / command line install and just removed all my installations. I will test that when I get it installed again. [...] [...] To prove my theory, I created a login for AdventureWorks, a replacement for Northwind and Pubs. I gave this login db_reader and db_writer rights, a common practice for a regular user. I then logged into this database with this login, using SSMS. Sure enough, under this regular user’s login, when I clicked on any server reports, I got a permission error. I haven’t checked database status reports yet, because I’ve been playing with silent / command line install and just removed all my installations. I will test that when I get it installed again. [...]

]]>