http://www.sqlmag.com/authors/author/author/5777842/rsscomment/5777842en-USFri, 25 May 2012 09:27:25 GMTFri, 25 May 2012 09:27:25 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-1#commentsAnchorMon, 19 Apr 2010 16:27:43 GMT
Good Beginner’s article.]]>David KananMon, 19 Apr 2010 16:27:43 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-1#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-101-stored-procedures#commentsAnchorWed, 20 May 2009 13:03:36 GMT
Nice step-by-step about the subject.]]>MarcosWed, 20 May 2009 13:03:36 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-stored-procedures#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-101-the-case-function#commentsAnchorThu, 16 Apr 2009 11:08:57 GMT
Try to copy and paste BOL next time! I got a better idea: write an article about copy and paste.]]>MarcosThu, 16 Apr 2009 11:08:57 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-the-case-function#commentsAnchorhttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorWed, 19 Nov 2008 03:40:22 GMT
Also see http://weblogs.sqlteam.com/peterl/archive/2008/10/10/Keep-track-of-all-your-jobs-schedules.aspx]]>mariusWed, 19 Nov 2008 03:40:22 GMThttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-1#commentsAnchorFri, 17 Oct 2008 12:46:05 GMT
Informative]]>RoyFri, 17 Oct 2008 12:46:05 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-1#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-5#commentsAnchorWed, 15 Oct 2008 10:11:03 GMT
Loved this article. I have printed it off for less knowledgeable users many times for use in understanding how to join tables within data mining applications, such as Crystal Reports from Business Objects. It is clear enough that the inexperienced user can pick up how to join talbes and a great reminder for those of us familiar with joins.]]>TIMWed, 15 Oct 2008 10:11:03 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-5#commentsAnchorhttp://www.sqlmag.com/article/tsql3/take-the-drudgery-out-of-making-sure-your-databases-are-being-backed-up-properly#commentsAnchorWed, 01 Oct 2008 10:52:33 GMT
This is a good idea. I have been setting up e-mail notification for each back up job. This one stop shop may be very helpful. I downloaded the code and will check it out.]]>DavidWed, 01 Oct 2008 10:52:33 GMThttp://www.sqlmag.com/article/tsql3/take-the-drudgery-out-of-making-sure-your-databases-are-being-backed-up-properly#commentsAnchorhttp://www.sqlmag.com/article/quering/t-sql101-lesson-2#commentsAnchorThu, 11 Sep 2008 14:07:56 GMT
Another good refresh in the basis of SQL. Thanks.]]>MarcosThu, 11 Sep 2008 14:07:56 GMThttp://www.sqlmag.com/article/quering/t-sql101-lesson-2#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-101-views#commentsAnchorThu, 04 Sep 2008 14:43:55 GMT
The endless dilema - use the resources wisely. Good text.]]>MarcosThu, 04 Sep 2008 14:43:55 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-views#commentsAnchorhttp://www.sqlmag.com/article/tsql3/a-quick-and-easy-way-to-view-errorlog-files#commentsAnchorTue, 12 Aug 2008 09:29:51 GMT
great script]]>BrandieTue, 12 Aug 2008 09:29:51 GMThttp://www.sqlmag.com/article/tsql3/a-quick-and-easy-way-to-view-errorlog-files#commentsAnchorhttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-1#commentsAnchorFri, 27 Jun 2008 08:35:48 GMT
Thank you. It’s a great article.]]>GokhanFri, 27 Jun 2008 08:35:48 GMThttp://www.sqlmag.com/article/tsql3/t-sql-101-lesson-1#commentsAnchorhttp://www.sqlmag.com/article/tsql3/take-the-drudgery-out-of-making-sure-your-databases-are-being-backed-up-properly#commentsAnchorFri, 02 May 2008 09:52:53 GMT
Like it but I do no know if I have a problem which I do not understand and your view does not handle. I have four entries for a full backup with different page counts but same physical device name and always one bf.file_ype = L. I think you are missing a grouping somewhere.]]>TerryFri, 02 May 2008 09:52:53 GMThttp://www.sqlmag.com/article/tsql3/take-the-drudgery-out-of-making-sure-your-databases-are-being-backed-up-properly#commentsAnchorhttp://www.sqlmag.com/article/tsql3/take-advantage-of-osql-and-bcp-without-having-to-remember-all-their-command-line-options#commentsAnchorThu, 17 Apr 2008 11:45:12 GMT
The txt file generated by the option OSQL in some cases it reads different from application to application. From the program EDIT (DOS) it reads with spaces within the text written. eg. H E L L O instead of HELLO. Using Multiedit the lines of the text file are broken in pieces which is quite particular. Why we have the file generated behave like that ?? Regards.]]>Jorge Oscar NicolasThu, 17 Apr 2008 11:45:12 GMThttp://www.sqlmag.com/article/tsql3/take-advantage-of-osql-and-bcp-without-having-to-remember-all-their-command-line-options#commentsAnchorhttp://www.sqlmag.com/article/tsql3/2-stored-procedures-to-tune-your-indexes#commentsAnchorThu, 17 Apr 2008 08:21:36 GMT
Bill, Can you clarify the following statement? More specifically why it is considered wasteful? "What stands out in this report is that the third index is a compound index that includes the same column as the clustered index (i.e., TheID). This is wasteful because each index row in the nonclustered index already contains a row-locater, which in this case, is the clustered index key (i.e., TheID)." Correct me if I’m wrong but by defining the non-clustered index as shown, you are essentially controlling the order in which your clustered key will be included in the non-clustered index. Had it not been specified, your index would have been “Age, TheID” instead of “TheID, Age” since the clustered index key is added to the end of the non-clustered index by default.]]>FredericThu, 17 Apr 2008 08:21:36 GMThttp://www.sqlmag.com/article/tsql3/2-stored-procedures-to-tune-your-indexes#commentsAnchorhttp://www.sqlmag.com/article/tsql3/2-stored-procedures-to-tune-your-indexes#commentsAnchorTue, 15 Apr 2008 11:57:45 GMT
Great article]]>ChristianTue, 15 Apr 2008 11:57:45 GMThttp://www.sqlmag.com/article/tsql3/2-stored-procedures-to-tune-your-indexes#commentsAnchorhttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorTue, 04 Mar 2008 22:27:35 GMT
Bvnashok, This stored procedure has been tested on a variety of SQL Server installations and has been running without error for years (the original code was developed in 2002 for SQL 2000). Can you please provide some details with regards to your exact version of SQL Server, whether or not it is a named instance, etc. Also, can you please enumerate the jobs that are running along with details of their schedules? My guess is that you have a job defined with a non-standard schedule that is causing the problem to present itself.]]>WilliamTue, 04 Mar 2008 22:27:35 GMThttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorhttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorTue, 04 Mar 2008 10:51:14 GMT
Hi, The script is useful, but it is not working in all conditions. I am getting the following error: Msg 512, Level 16, State 1, Procedure sp_ShowJobSchedules, Line 13 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. It would be nice, if the scripts are completed tested and then post to public.]]>ASHOKTue, 04 Mar 2008 10:51:14 GMThttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorhttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorFri, 15 Feb 2008 09:05:59 GMT
Be nice to associate owner and DB with this info. :)]]>peteFri, 15 Feb 2008 09:05:59 GMThttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorhttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorWed, 13 Feb 2008 10:54:53 GMT
Good stuff]]>JohnWed, 13 Feb 2008 10:54:53 GMThttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorhttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorFri, 01 Feb 2008 14:35:43 GMT
I’ve been looking for something like this for a while. Awesome!]]>JustinFri, 01 Feb 2008 14:35:43 GMThttp://www.sqlmag.com/article/tsql3/stored-procedure-documents-scheduled-jobs-in-sql-server#commentsAnchorhttp://www.sqlmag.com/article/tsql3/take-advantage-of-osql-and-bcp-without-having-to-remember-all-their-command-line-options#commentsAnchorMon, 12 Nov 2007 22:39:02 GMT
This is a great SP...one note though, if your server has a named instance SERVER\INSTANCE you will need to modify the parm a bit to add the parameter "-S" and your server name and instance. Other than that, it works as documented. Thanks Bill!]]>PaulMon, 12 Nov 2007 22:39:02 GMThttp://www.sqlmag.com/article/tsql3/take-advantage-of-osql-and-bcp-without-having-to-remember-all-their-command-line-options#commentsAnchorhttp://www.sqlmag.com/article/tsql3/a-quick-and-easy-way-to-view-errorlog-files#commentsAnchorFri, 05 Oct 2007 07:47:53 GMT
Great, it’s working!]]>AlexanderFri, 05 Oct 2007 07:47:53 GMThttp://www.sqlmag.com/article/tsql3/a-quick-and-easy-way-to-view-errorlog-files#commentsAnchorhttp://www.sqlmag.com/article/tsql3/retrieve-triggers-from-the-sql-command-prompt#commentsAnchorTue, 12 Jun 2007 05:34:34 GMT
This is a very helpful script. Especially for someone who needs to know all the tables with triggers in a database.]]>DelfoeTue, 12 Jun 2007 05:34:34 GMThttp://www.sqlmag.com/article/tsql3/retrieve-triggers-from-the-sql-command-prompt#commentsAnchorhttp://www.sqlmag.com/article/internet/searching-the-web-for-sql-topics-give-sql-hunter-a-try#commentsAnchorMon, 11 Jun 2007 08:42:20 GMT
Cool site]]>JTMon, 11 Jun 2007 08:42:20 GMThttp://www.sqlmag.com/article/internet/searching-the-web-for-sql-topics-give-sql-hunter-a-try#commentsAnchorhttp://www.sqlmag.com/article/tsql3/a-quick-and-easy-way-to-view-errorlog-files#commentsAnchorThu, 31 May 2007 07:07:45 GMT
great stuff]]>YannickThu, 31 May 2007 07:07:45 GMThttp://www.sqlmag.com/article/tsql3/a-quick-and-easy-way-to-view-errorlog-files#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorWed, 29 Nov 2006 13:24:00 GMT
Sorry ignore my previous comment, I re-read the article.]]>JayWed, 29 Nov 2006 13:24:00 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorWed, 29 Nov 2006 12:58:13 GMT
Nice tool but it only returns the results for my spid (using sql server 2000) how can it be changed to show the activity for all current logged on users?]]>JayWed, 29 Nov 2006 12:58:13 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorMon, 16 Oct 2006 09:38:10 GMT
The script was indeed written for SQL2000, service pack 3 (and up). Make sure you are running the latest service pack. As for your suggestions, they sound great. The source is open, knock yourself out.]]>WilliamMon, 16 Oct 2006 09:38:10 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorSat, 14 Oct 2006 10:36:19 GMT
Despite the author’s note that he wrote this for SQL 2000 (perhaps an editing error), based on my tests, the script does NOT work on SQL 2000, and was written for SQL 2005. (there is no sql_handle field in sysprocesses on my SQL 2000, but there is in 2005) Very interesting utility--excellent idea, solving a problem that I have had several times trying to diagnose a slow running SQL Server. It is a nice utility in that it displays only the activity that is occurring, vs. running sp_who and sysprocesses and having to scroll through the results. Having just tested it for the first time, I’m finding the output very difficult to review and scan, since each SPID has 3 different result sets. Perhaps it could be tweaked to insert the data into a temp table that can accomodate all of the fields and produce a more readable output.]]>StephenSat, 14 Oct 2006 10:36:19 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorFri, 06 Oct 2006 04:23:21 GMT
First line of third paragraph states this code was written for SQL2000. You can block your own spid, but you won’t be able to see if you are blocking some other process.]]>WilliamFri, 06 Oct 2006 04:23:21 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorThu, 05 Oct 2006 13:14:10 GMT
Why is this code showing my own process? Does it work on SQL 2005? I think that all articles should specify SQL200, SQL 2005 or both.]]>RudyThu, 05 Oct 2006 13:14:10 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorWed, 04 Oct 2006 08:50:15 GMT
doesn’t work as advertised]]>TIMWed, 04 Oct 2006 08:50:15 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorFri, 29 Sep 2006 06:39:28 GMT
I just used this proc to show how every time a user was hitting a particular button on the app, the server start to grind. Pushing the button caused a script to run that updated every ID in a table to itself. Yes, you read that right. I don’t know who wrote that code, but it is not only useless it brings the server to its knees. Did I mention the ID had a clustered index on it?]]>WilliamFri, 29 Sep 2006 06:39:28 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorWed, 27 Sep 2006 07:27:13 GMT
Not bad!]]>RobertWed, 27 Sep 2006 07:27:13 GMThttp://www.sqlmag.com/article/tsql3/prove-that-the-database-isn-t-to-blame#commentsAnchorhttp://www.sqlmag.com/article/tsql3/stored-procedure-searches-for-strings#commentsAnchorMon, 24 Jul 2006 11:44:58 GMT
Hey, this is pretty neat. It is like "grep" for SQL.]]>WilliamMon, 24 Jul 2006 11:44:58 GMThttp://www.sqlmag.com/article/tsql3/stored-procedure-searches-for-strings#commentsAnchor