May 9, 2017 at 2:55 pm
Hi,
\setup.exe
/Action=Install
/QS
/SQMREPORTING=0
/IACCEPTSQLSERVERLICENSETERMS
/ERRORREPORTING=0
/Features=ADV_SSMS,BC,BOL,Conn,FullText,RS,SQL
....
/INSTANCEID="SQLPROD01"
/INSTANCENAME="SQLPROD01" will install
1.SQL instance SQLPROD01
2.Create reporting services SQLPROD01
3.on sql instance SQLPROD01 create 2 databaases
ReportServer$SQLPROD01
ReportServer$SQLPROD01Tempdb
Is any we can submit Specific names for Reporting services database during command prompt installation? Reason
We use powershell to install and manage our sql servers , $ sign in database names cause many problem (I am aware that we can can configure reporting services later using /RSINSTALLMODE=FilesOnlyMode or installing services after sql isnatnace created)
Thank you
May 10, 2017 at 11:28 am
ebooklub - Tuesday, May 9, 2017 2:55 PMHi,\setup.exe
/Action=Install
/QS
/SQMREPORTING=0
/IACCEPTSQLSERVERLICENSETERMS
/ERRORREPORTING=0
/Features=ADV_SSMS,BC,BOL,Conn,FullText,RS,SQL
....
/INSTANCEID="SQLPROD01"
/INSTANCENAME="SQLPROD01" will install
1.SQL instance SQLPROD01
2.Create reporting services SQLPROD01
3.on sql instance SQLPROD01 create 2 databaases
ReportServer$SQLPROD01
ReportServer$SQLPROD01Tempdb
Is any we can submit Specific names for Reporting services database during command prompt installation? Reason
We use powershell to install and manage our sql servers , $ sign in database names cause many problem (I am aware that we can can configure reporting services later using /RSINSTALLMODE=FilesOnlyMode or installing services after sql isnatnace created)Thank you
The default names would be ReportServer and ReportServerTempdb. Not sure how you ended up with those names - are those the names you got for all tests - with the Dollar sign? Did you specify those names somewhere in the unattended installation script (didn't know you could)? Were any existing ReportServer databases on the server at the time?
Sue
May 10, 2017 at 11:53 am
ebooklub - Tuesday, May 9, 2017 2:55 PMHi,\setup.exe
/Action=Install
/QS
/SQMREPORTING=0
/IACCEPTSQLSERVERLICENSETERMS
/ERRORREPORTING=0
/Features=ADV_SSMS,BC,BOL,Conn,FullText,RS,SQL
....
/INSTANCEID="SQLPROD01"
/INSTANCENAME="SQLPROD01" will install
1.SQL instance SQLPROD01
2.Create reporting services SQLPROD01
3.on sql instance SQLPROD01 create 2 databaases
ReportServer$SQLPROD01
ReportServer$SQLPROD01Tempdb
Is any we can submit Specific names for Reporting services database during command prompt installation? Reason
We use powershell to install and manage our sql servers , $ sign in database names cause many problem (I am aware that we can can configure reporting services later using /RSINSTALLMODE=FilesOnlyMode or installing services after sql isnatnace created)Thank you
Interesting... I recently set up a SQL 2016 instance for SSRS using the GUI (making a boring test server that will be blown away in a week). I didn't even bother checking the database names but I saw the same thing. Are you using SQL 2016 as well?
As a thought about getting around that $ in the database name, what if you surround your powershell stuff with single quotes instead of double quotes? In powershell, a single quote will take the literal of the $ instead of the variable associated with the $. That should fix the powershell.
see:
PS C:\> $test= "hello"
PS C:\> echo $test
hello
PS C:\> $test= "hello$world"
PS C:\> echo $test
hello
PS C:\> $test= 'hello$world'
PS C:\> echo $test
hello$world
PS C:\>$test2 = $test
PS C:\>echo $test2
hello$world
As seen above, single quotes inside powershell should fix the issue for you, no? That should also make the powershell a touch more future proof in the event MS does this with more databases.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
May 10, 2017 at 12:00 pm
Never seen that - and the documentation doesn't mention name changes. It lists the defaults as ReportServer and ReportServerTempdb -
Report Server Database (SSRS Native Mode)
Sue
May 10, 2017 at 12:13 pm
Sue_H - Wednesday, May 10, 2017 12:00 PMNever seen that - and the documentation doesn't mention name changes. It lists the defaults as ReportServer and ReportServerTempdb -
Report Server Database (SSRS Native Mode)Sue
That was my thought too... I didn't install it from the command line; I used the GUI as it was going to be a quick install. I am not 100% sure why it installed it that way. And google isn't much help on this either.
Wonder if I did something goofy in the SSRS install via the GUI or if the version of the SQL installer I am using does some undocumented things?
Everything I see online says it should use the default names, but mine did not and I don't remember (or know why) I'd specify odd names like that.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
May 10, 2017 at 12:44 pm
installing as new instance of sql2008R2
server already has 2 more named instances (2008R2 and SQL2014)
we automating installation of SQL in our shop (similar to azure and amazon), "click button and server is ready and configured in 15 minutes including all futures you selected",
it is important don't have $ in name of Reporting databases since a lot of monitoring script starts automatically after server is installed ( done PowerShell ) and they can't process name with $ in middle
we install only named instances
bellow all option submitted for install
\\installRepository\mssql\2008R2\ENT\setup.exe
/Action=Install
/QS
/SQMREPORTING=0
/IACCEPTSQLSERVERLICENSETERMS
/ERRORREPORTING=0
/Features=ADV_SSMS,BC,BOL,Conn,FullText,RS,SQL
/SQLSVCACCOUNT="mydomain\dba"
/SQLSVCPASSWORD="strong_pwd"
/SQLSVCSTARTUPTYPE="Manual"
/AGTSVCACCOUNT="mydomain\dba"
/AGTSVCPASSWORD="strong_pwd"
/AGTSVCSTARTUPTYPE="Manual"
/SQLSYSADMINACCOUNTS="mydomain\dba" "mydomain\dba1" "mydomain\dba2"
/SECURITYMODE=SQL
/SAPWD="AnotherStrong#pwd"
/BROWSERSVCSTARTUPTYPE="Disabled"
/SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
/NPENABLED=0
/TCPENABLED=1
/INSTANCEID="SQLPROD01"
/INSTALLSQLDATADIR="C:\DEV"
/SQLUSERDBDIR="C:\DEV\MSSQL10_50.SQLPROD01\MSSQL\Data"
/SQLUSERDBLOGDIR="C:\DEV\MSSQL10_50.SQLPROD01\MSSQL\Data"
/SQLTEMPDBDIR="C:\DEV\MSSQL10_50.SQLPROD01\MSSQL\Data"
/SQLTEMPDBLOGDIR="C:\DEV\MSSQL10_50.SQLPROD01\MSSQL\Data"
/SQLBACKUPDIR="C:\backup\dump"
/INSTANCENAME="SQLPROD01"
/FTSVCACCOUNT="mydomain\dba"
/FTSVCPASSWORD="strong_pwd"
/FTSVCSTARTUPTYPE="Manual"
/RSSVCACCOUNT="mydomain\dba"
/RSSVCPASSWORD="strong_pwd"
/RSSVCStartupType="Manual"
I am wondering if Microsoft have hidden installation parameter (I have seen it before with install option "allow install on shared drive") where "ReportServer" could be overwritten
May 10, 2017 at 12:57 pm
Hmmmm.... not sure why that would be then.
Can you run a SQL script to rename the database post install? Is that an option for your method or no?
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
May 10, 2017 at 1:17 pm
bmg002 - Wednesday, May 10, 2017 12:57 PMHmmmm.... not sure why that would be then.Can you run a SQL script to rename the database post install? Is that an option for your method or no?
I think they would still need to change the database in Reporting Services Configuration Manager though to get the dependencies corrected.
I was just checking the registry on those - interesting that the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Services\ReportServer
Has LName and Name. LName is ReportServer$ and Name has ReportServer. Same with some of the other services in there though.
Sue
May 10, 2017 at 1:41 pm
>Can you run a SQL script to rename the database post install? Is that an option for your method or no?
if ReportServer db is renamed after install I will have manually Reconfigure SSRS using SSRS configuration manager(change db names ,correct security key...), unless the is some script could be executed that will update report config file and entry in system tables of master
May 10, 2017 at 1:44 pm
ebooklub - Wednesday, May 10, 2017 12:44 PMI am wondering if Microsoft have hidden installation parameter (I have seen it before with install option "allow install on shared drive") where "ReportServer" could be overwritten
I've seen the same on unattended installs but usually it shows up if you get the parameters yourself from the setup.exe. I just checked - didn't find anything.
The one I'm wondering about is if it makes a different if you specify the /RSINSTALLMODE and set it to Default. I didn't see that in your parameters.
I've never paid that much attention but if you don't specify the mode, it defaults to FilesOnly. In other words the default is not DEFAULT. So I'm wondering if you didn't end up with FilesOnly - looks like you would have. And maybe those were temporary databases until the configuration is done.
Sue
May 10, 2017 at 1:53 pm
I tried installation with
/RSINSTALLMODE=FilesOnlyMode
yes SSRS installed and no ReportServer databases created
I would probably will use this option and create PowerShell script that will run after installation and configure Reporting Services including creation of databases
Goal of installation is full automation (user/dba/develpoer should not spend time or have knowledge how to install and configure server) 🙂
May 10, 2017 at 2:18 pm
ebooklub - Wednesday, May 10, 2017 1:53 PMI tried installation with
/RSINSTALLMODE=FilesOnlyMode
yes SSRS installed and no ReportServer databases createdI would probably will use this option and create PowerShell script that will run after installation and configure Reporting Services including creation of databases
Goal of installation is full automation (user/dba/develpoer should not spend time or have knowledge how to install and configure server) 🙂
I think that's what you have to do at this point. Those names still seem weird....wish we could've figured that out.
Anyway, you can make calls to the Reporting Services WMI provider to do the rest of the configuration, which will have all the dependencies set, using Powershell. So it is doable to do it this way and still have it fully automated.
Sue
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply