SQL Server Management Studio Show last executed query
I am looking for a way for SQL Server Management studio to show me the last SQL query that was run. For example, when I make modifications to a table in the designer mode, I will eventually want to make the same changes to the production DB without recreating the entire table. I’m looking for functionality similar to PHPMyAdmin for MySQL which tells you the last query ran and the results of the query at the top of the page after the modifications are complete.
We are moving an Access based corporate front-end into a Web-based App [closed]
Closed 5 years ago.
Does the deprecation of mysql_* functions in PHP carry over to other Databases(MSSQL)?
I’m not talking about MySQL, I’m talking about Microsoft SQL Server I’ve been aware of PDO for quite some time now, standard mysql functions are dangerous and should be avoided. http://php.net/manual/en/function.mysql-connect.php But what about the MSSQL function in PHP? They are, for most purposes, identical sets of functions, but the PHP page describing mssql_* carries […]
Calling MSSQL stored procedure from Zend Controller ? Any other approaches?
MSSQL and DB, Zend as PHP Framework,
Idea to develop a caching server between IIS and SQL Server
I work on a few high traffic websites that all share the same database and that are all heavily database driven. Our SQL server is max-ed out and, although we have already implemented many changes that have helped but the server is still working too hard.
Microsoft SQL Server Usage Data
I want to build a usage scanner for SQL Server to gather information about which user performed which query, how much time it took, etc., similar to Snowflake.
Using xml datatype to store a “shopping cart”
For my final project in school we have to develop an online shop. This shop should have a cart where items can be placed whether or not you are logged in. If you log out the cart shouldn’t empty and should still be shown.
Algorithm to denormalize database
I have built a QlikView script generator (QVS), that can be used to generate large script files for data imports from SQL Server to QlikView.
Scalability: How does splitting a database table work on different replicated SQL Servers?
I would like to know more about the general concepts behind dividing data of a database into different servers. For example, suppose I have a SQL Server database which has a massive table. Assume one single server cannot handle the amount of data in this table. I would like to break that table down and split its contents among different servers with an identical database (replicated).
Better way of storing key-value pairs in the database?
I have a C#/SQL Server program that sometimes needs to store data. The data could be a response from a web service, a result of a database query, or any number of other things. There’s no way of knowing before the data is stored how many fields it might have or what the data structure might be. We have this kind of painful table we’re using for this… four columns and lots of rows. An example of the data might be easier than an explanation.