• Expiring Oracle 11g Passwords

    On an ongoing basis I've been maintaining Oracle 11g databases for performance testing, development and certification.  Because I switch back and forth between Oracle and SQL Server, I've been caught up a few times where the passwords for a given instance of Oracle have expired.  It always seems to hit at the most inopportune time.  And of course I never remember exactly what the problem is, so I end up spending hours pour…
    • Fri, Sep 18 2009
  • ProjectWise Performance Tuning: Part 1

     

    Over the past few years a large part of my job function has been to do performance testing of ProjectWise.  I'm titling this article as Part 1 because the one thing I've learn is that performance tuning is an ongoing effort.  With each workflow, network configuration, database and database configuration we are constantly finding ways to improve the performance of ProjectWise.  The items I will be discussing in this…

    • Thu, Apr 23 2009
  • Session Debug and Logging Database Commands

     

    Session Debug:

    Session Debug has been in MicroStation since the MicroStation Database connections were introduced.  This handy command gives you insight into the SQL that is being generated from MicroStation or the MicroStation Database API.  It is probably the first and foremost tool for investigating Database connectivity or SQL Syntax issues.

    The Session Debug command is part of the Database MDL app…

    • Wed, Mar 11 2009
  • Orphaned User Migrating from SQL Server 2000 to 2005

     

    In SQL Servers 2005 the concept of a schema has been added to the database.  ProjectWise V8i handles the schema as part of the qualifying the object names in the database.  In earlier versions of ProjectWise the additional schema layer can be handled as long as the schema name is the same as the user name and more so the login name.

    Many times with SQL Server databases the database is left to be owned by the System…

    • Thu, Mar 5 2009
  • 32 Bit Database Connectivity on a 64 Bit OS

    As I've begun migrating to 64 bit Operating Systems, one thing that catches me off guard the most is setting up and using the proper ODBC drivers and OLEDB providers.  The key to getting the right one configured is to remember that if you are using a 32 bit application you want to use the 32 bit version of the ODBC driver and 32 bit version of the OLEDB provider.  If you are using a 64 bit application than you want to use…
    • Wed, Mar 4 2009
  • Are you using SQL Server 2005? Are you really using SQL Server 2005?

    As SQL Server 2005 hit the market it did so with some impressive new features and functionality.  One of the new features was to allow Database Administrators to set the SQL Server Compatibility Level of a database.  This is useful if you are relying on a feature in an older version of SQL Server that is no long supported in SQL Server 2005.  It is also a good safe guard for migrating a database application forward to the latest…

    • Tue, Feb 24 2009
  • The MicroStation Database Element

    The purpose of the MicroStation database element is to allow the user to automatically connect to an ODBC or OLEDB database when opening a design file.  When you start MicroStation with the -WDODBC or -WDOLEDB command line options, MicroStation loads the appropriate database element from the design file.  The database element contains the ODBC data source name or the OLEDB .UDL filename.  From this information MicroStation…

    • Mon, Dec 22 2008
  • Microsoft SQL Server OSQL.exe Tool

    Looking for a quick command line approach to accessing Microsoft SQL Server? 

    With SQL Server 2005 there is a command line utility called OSQL.  This tool can be used to connect to a SQL Server database and perform various SQL commands at a command prompt.  The tool can be used to access SQL Server Express, Standard and Enterprise editions.

    At the command prompt simply key in OSQL.exe followed by the login credentials…

    • Fri, Dec 19 2008