Hi, I tried filtered indexes, it can be useful here are my tests: http://community.ugiss.org/blogs/sgovoni/archive/2009/09/12/filtered-indexes.aspx...
you could use a statement if...else:
if (SELECT count(*) as tblCount from myTable) = 0
take a look at this link , you can find a small script (for SQL Server 2005 or higher) showing for each database, the data size of log...
see this link http://support.microsoft.com/kb/321686.
Another way to export query result set in Excel: How to export query result set...
Can I easily know the old and new value of a field in the case run a command to update ?
From Books OnLine:
The fn_get_sql function returns information that is similar to the DBCC INPUTBUFFER command. The following are examples of when...
Thanks for your answer.
I still have a problem: use the function:: fn_get_sql () with SQL Server 2000 within a trigger, such as:
I have a mixed situation: some installation using SQL Server 2000, other installations SQL Server 2005. Well, with SQL Server...
thanks for replay, I store the results in a table with field EventInfo ad VarChar(2000) but only first 255 characters are stored....
within a trigger I use the command "DBCC INPUTBUFFER (@@SPID) WITH NO_INFOMSGS" to capture the statement that the client has sent to the server....
I was to do the same thing [:D].
We arrived to solving the problem [:D], summarized in this article.
Thanks to all!
could you post a script for the creation of tables and the inclusion of some test data ?
and thanks for your reply.
The application in version 2.0 uses DB-Library, while the application in version 3.0 uses OLE DB....
Even for me is not possible to control the activation of a trigger, the only way that I know is to customize the flow with the option UPDATE.
could you post the error message ?
By default SQL Server 2005 Express, Evaluation, and Developer edition allow local client connections...
any default value should be the same type of field, in your case having a field type INTEGER and the default value must be an INTEGER or...
I am developing an application that uses OLE DB to connect to SQL Server 2000; originally the application was using DB-Library to connect to SQL...
Yes, the trigger is fired each time that table is updated, but if you use the UPDATE (column) clause you can restrict the operations...
I read that writing query with filtering criteria fully qualified greatly reduces the I/O operation.
So I'm changing the WHERE clause which are...
Separate names with a comma.