string SQL = "CREATE TABLES [dbo].[ErrorLog]( \n"
           + "    [ErrorLogID] [int] IDENTITY(1,1) NOT NULL, \n"
           + "    [ErrorTime] [datetime] NOT NULL, \n"
           + "    [UserName] [sysname] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, \n"
           + "    [ErrorNumber] [int] NOT NULL) \n"
           + "GO \n"
           + "SELECT * FROM TABLE ErrorLog";

Dim SQL As String
SQL = "CREATE TABLES [dbo].[ErrorLog]( " + char(10) _
    + "    [ErrorLogID] [int] IDENTITY(1,1) NOT NULL, " + char(10) _
    + "    [ErrorTime] [datetime] NOT NULL, " + char(10) _
    + "    [UserName] [sysname] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, " + char(10) _
    + "    [ErrorNumber] [int] NOT NULL) " + char(10) _
    + "GO " + char(10) _
    + "SELECT * FROM TABLE ErrorLog"

<?php
string s$SQL = "CREATE TABLES [dbo].[ErrorLog]( \n"
     . "    [ErrorLogID] [int] IDENTITY(1,1) NOT NULL, \n"
     . "    [ErrorTime] [datetime] NOT NULL, \n"
     . "    [UserName] [sysname] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, \n"
     . "    [ErrorNumber] [int] NOT NULL) \n"
     . "GO \n"
     . "SELECT * FROM TABLE ErrorLog";
?>

$SQL = 'CREATE TABLES [dbo].[ErrorLog]( \n'
     . '    [ErrorLogID] [int] IDENTITY(1,1) NOT NULL, \n'
     . '    [ErrorTime] [datetime] NOT NULL, \n'
     . '    [UserName] [sysname] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, \n'
     . '    [ErrorNumber] [int] NOT NULL) \n'
     . 'GO \n'
     . 'SELECT * FROM TABLE ErrorLog';

var
  SQL string;
begin
  SQL := 'CREATE TABLES [dbo].[ErrorLog]( ' + #10
       + '    [ErrorLogID] [int] IDENTITY(1,1) NOT NULL, ' + #10
       + '    [ErrorTime] [datetime] NOT NULL, ' + #10
       + '    [UserName] [sysname] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, ' + #10
       + '    [ErrorNumber] [int] NOT NULL) ' + #10
       + 'GO ' + #10
       + 'SELECT * FROM TABLE ErrorLog';
end;

SQL = 'CREATE TABLES [dbo].[ErrorLog]( \n'
   << '    [ErrorLogID] [int] IDENTITY(1,1) NOT NULL, \n'
   << '    [ErrorTime] [datetime] NOT NULL, \n'
   << '    [UserName] [sysname] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, \n'
   << '    [ErrorNumber] [int] NOT NULL) \n'
   << 'GO \n'
   << 'SELECT * FROM TABLE ErrorLog'

std::string SQL;
SQL = "CREATE TABLES [dbo].[ErrorLog]( \n"
    + "    [ErrorLogID] [int] IDENTITY(1,1) NOT NULL, \n"
    + "    [ErrorTime] [datetime] NOT NULL, \n"
    + "    [UserName] [sysname] COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, \n"
    + "    [ErrorNumber] [int] NOT NULL) \n"
    + "GO \n"
    + "SELECT * FROM TABLE ErrorLog";

Thanks,
Goran Bogdanovic
ApexSQL Edit Development Team Leader

ApexSQL Code

As I said, new Code 2008.04 has been released a week ago. We removed offline help files (CHM) which reduced the size of the installer resulting in lighter download size. We also fixed a couple of bugs in this release I already talked about in one of my previous posts – find it here. You can check the release notes and download the new release from our downloads page.

SimpleDataFramework for Code got updated as well thanks to Rob, its author. Framework is now in beta phase, we’re encouraging everyone to try it out (especially since we’re offering ApexSQL Code 2008 copy for free). So, what’s new? Lots of bug fixes and some changes as well. Rob separated his SDF project from web project, so now it’s shipped as standalone library. Demo project is in the archive featuring AdventureWorksLT example. To run it, you’ll only have to execute sql_StoredProcedures.sql procedure on your AWorksLT database (this stored procedure is generated with sdf_SqlProcs.ptpx Code template). Starting UI page (Table of tables) got updated to show some details about the tables as well. All columns can be shown/hidden optionally. See some shots of the UI below, it looks really nice.

ApexSQL Log

We’re about to release new Log testing candidate to Q&A today. This label has several new features and lots of bug fixes – you can find all the details in my previous blog post. But the development continues. We intend to make updates to our internal output processing components which will give us more room for improving the output (file exports from Log) and CLI processing. This would also help us add new export formats eventually. As mentioned, we are considering including a new export format: HTML. Export to HTML with produce nice and clean HTML code/page with the results of your auditing session nicely formatted. However, we would really love to hear your thoughts about this, it would certainly help us decide whether it’s worth adding or not.

One of the improvements is direct export to file from GUI. So far, you had to use CLI if you wanted to skip loading data to the grid and now you can use a comfortable GUI Wizard to do the same thing. We have added a new step to the Wizard where one can specify whether he wants to redirect auditing output directly to a file or use the grid as usual

As shown on the screenshot, you can generate Undo and Redo scripts, output transactions and operations info into XML, CSV, SQL script or SQL BULK files directly from GUI. We are also targeting on improving the CSV and XML output. For example, with CSV, we will be eliminating the one-to-many presentation of audit data to make it more readable. We’re also considering adding a new export format: HTML. If you find this useful, please let us know. The more positive feedback we get, the more likely we’ll decide to implement it.

We applied some minor UI changes to the Filter step in Log Filter Wizard suffered some minor UI changes . We have a new node and got a new tab for choosing columns. I wrote about this step earlier, you can find all the details in that blog post.

Development is now ongoing to apply column filtering to the export files.

Going further, another Wizard step is introduced for listing the details about the current auditing session. Users will be able to see the summary of their data and log sources, chosen filters etc. and proceed to the next step if everything is OK or go back and make necessary changes if needed. It looks something like this:

Finally, we’ll have a screen where you can watch the processing progress showing some useful info along the way. Once it finishes, UI is ready for another auditing session.