Ok. What you do is build an ODBC data connection on the web server, pointing to the SQL server database.
Then, in your ASP pages, you point to the ODBC connection, and use that as the device to connect to the dynamic content on the SQL server database.
So, if you can write ASP code, then you should know how to build the ODBC connection in the ASP. But here is a sample:
Conn = "Provider=SQLODBC;Persist Security Info=True;Initial Catalog=MYDATABASE;Data Source=192.168.1.1;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=192.168.1.1;Use Encryption for Data=False;Tag with column collation when possible=False;User Id=USERACCT;password=PASSWORD"
Now, that line would actually build the ODBC connection, instead of calling one that is already built on the web server. You can do it either way. If you don't want to build the ODBC connections on the web server, then you can just code it, like in my example. Either way works.
Then, you just have your ASP page pullfrom the SQL server to get its content. You can also pass parameters that way. That is what you are seeing in the URLs you posted. ASP parameters are being sent in the URL; the receiving ASP page will take the parameter passed, and process it, using it to generate more dynamic content.
hope this helps