Reply to thread

Message

<blockquote data-quote="rsbrux" data-source="post: 1300685" data-attributes="member: 49539">I'm not sure that's a good idea. Some people will just try and install MP and need to be warned that MS SQL Server requires them to install it themselves before installing MP TV Server.&nbsp; BTW, the defaults in the SQL Server DB connection dialog in the 1.36 installation didn't work for me:<ol>
<li data-xf-list-type="ol">An instance name is required.&nbsp; The MS SQL configuration script I published on the wiki for MS SQL Server 2017 still works and uses an instance name of &quot;SQLEXPRESS&quot;. For MS SQL Server, the first field in the connection dialog should therefore be &quot;&lt;computer name&gt;\SQLEXPRESS&quot; not just &quot;&lt;computer name&quot;.</li>
<li data-xf-list-type="ol">The dependency is incorrect. It should be &quot;MSSQL$SQLSERVER&quot;, not &quot;SQLBrowser&quot;.&nbsp; This problem goes back to MP 1.27.</li>
</ol>With these changes the DB connection test succeeds.</blockquote>

[QUOTE="rsbrux, post: 1300685, member: 49539"] I'm not sure that's a good idea. Some people will just try and install MP and need to be warned that MS SQL Server requires them to install it themselves [I]before[/I] installing MP TV Server. BTW, the defaults in the SQL Server DB connection dialog in the 1.36 installation didn't work for me: [LIST=1] [*]An instance name is required. The MS SQL configuration script I published on the wiki for MS SQL Server 2017 still works and uses an instance name of "SQLEXPRESS". For MS SQL Server, the first field in the connection dialog should therefore be "<computer name>\SQLEXPRESS" not just "<computer name". [*]The dependency is incorrect. It should be "MSSQL$SQLSERVER", not "SQLBrowser". This problem goes back to MP 1.27. [/LIST] With these changes the DB connection test succeeds. [/QUOTE]

Verification