Forum Replies Created

Viewing 11 posts - 1 through 11 (of 11 total)

  • Reply To: Getting Close

    My guess for the SQL Server 2019 release date is July 1st, 2019

  • RE: SQL Server Tuning Skills

    Amazon link  You missed a great opportunity to plug Grant Fritchey's excellent book 🙂

  • RE: Finding table name based on a specific value

    query does not take into account the table schema so it is fails in my database.  It will only work if all tables are in the dbo schema, which is...

  • RE: Find all published tables with row counts and table size

    Thanks, but this script only works if you have a local distribution database (and that it is named [distribution]).  The publication/article data is available in each publisher DB in [dbo].[syspublications] and [dbo].[sysarticles]...

  • RE: Validating null values in a column without using ISNULL or NVL.

    I ran the code as is and got:

    Msg 207, Level 16, State 1, Line 10

    Invalid column name 'A'.

    Msg 207, Level 16, State 1, Line 10

    Invalid column name 'B'.

    Msg 207, Level...

  • RE: Get Server version Info

    Thanks. I have verified ServerProperty does work as far back as SQL Server 2000. Couldn't really find a way to differentiate between server and non-server versions so just...

  • RE: Open transactions on a database

    Nice script. Three(minor) comments:

    First, ** While running the below query if you find any query which ** is repeated in the comment header.

    Second, I...

  • RE: Using APPLY to make your queries DRYer

    Nice article. Learned something really useful (and powerful) today. Execution plans and page reads are identical, yet it is much easier to read and maintain now. Thank...

  • RE: Start job on another server

    I use PowerShell in a job step, it is very easy...

    $sqlConnection = new-object System.Data.SqlClient.SqlConnection

    $sqlConnection.ConnectionString = 'server=myserver;integrated security=TRUE;database=msdb'


    $sqlCommand = new-object System.Data.SqlClient.SqlCommand

    $sqlCommand.CommandTimeout = 0

    $sqlCommand.Connection = $sqlConnection

    $sqlCommand.CommandText= "exec...

  • RE: Changing the Past

    For all of you that have perfect data entry personnel, or don't have to deal with 3rd shift temp workers :-), then changing bad data is nothing to worry about....

  • RE: Decoupling in Relational Databases

    the biggest take-away from this article should be: never use an IDENTITY primary key field in a many-to-many (junction, link, bridge, associative, etc.) table. It provides no value...

Viewing 11 posts - 1 through 11 (of 11 total)