Reply to thread

Message

<blockquote data-quote="sjevtic" data-source="post: 1004564" data-attributes="member: 118214">I provided a SQL query that will perform a particular update on a MS SQL Server database. You can execute that via any interface you choose, such as SQL Server's own management tools, or via a client application such as Access or even a VBScript script that connects to the database via ODBC or some other means. So, it's not really a matter of choosing an extension for the file as much as it is deciding how you plan to execute it.&nbsp;I also demonstrated how to execute the query using &quot;sqlcmd&quot;, which is a command line client utility that ships with MS SQL Server. To use it, you literally just execute the &quot;sqlcmd&quot; command with the arguments I provided from a cmd.exe session subject to the limitations I described.Unfortunately, every database vendor implements things a little differently, and since you're using MySQL, you'll have to make the necessary changes to execute the query there. As @<a href="https://forum.team-mediaportal.com/members/mm1352000.82144/" target="_blank">mm1352000</a> already pointed out, MySQL's command line utility is called &quot;mysql&quot; instead of &quot;sqlcmd&quot; and has a different interface. As you have both already observed, SQL Server also adds &quot;dbo_&quot; prefixes to table names, whereas MySQL does not. Unfortunately, I don't have a MySQL setup right now, so I am unable to provide specific examples for MySQL. Sorry.&nbsp;Sasha</blockquote>

[QUOTE="sjevtic, post: 1004564, member: 118214"] I provided a SQL query that will perform a particular update on a MS SQL Server database. You can execute that via any interface you choose, such as SQL Server's own management tools, or via a client application such as Access or even a VBScript script that connects to the database via ODBC or some other means. So, it's not really a matter of choosing an extension for the file as much as it is deciding how you plan to execute it. I also demonstrated how to execute the query using "sqlcmd", which is a command line client utility that ships with MS SQL Server. To use it, you literally just execute the "sqlcmd" command with the arguments I provided from a cmd.exe session subject to the limitations I described. Unfortunately, every database vendor implements things a little differently, and since you're using MySQL, you'll have to make the necessary changes to execute the query there. As @[URL='https://forum.team-mediaportal.com/members/mm1352000.82144/']mm1352000[/URL] already pointed out, MySQL's command line utility is called "mysql" instead of "sqlcmd" and has a different interface. As you have both already observed, SQL Server also adds "dbo_" prefixes to table names, whereas MySQL does not. Unfortunately, I don't have a MySQL setup right now, so I am unable to provide specific examples for MySQL. Sorry. Sasha [/QUOTE]

Verification