Re: SQLServer 2000 SP 1 Bug
From: BP Margolin (bpmargo@attglobal.net)
Date: 12/12/02
- Next message: Kimberly L. Tripp: "Re: SQL Server 7 Service Account Name"
- Previous message: Russell Fields: "Re: Creating user after backup"
- In reply to: Jim Barry: "SQLServer 2000 SP 1 Bug"
- Next in thread: Jasper Smith: "SQLServer 2000 SP 1 Bug"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "BP Margolin" <bpmargo@attglobal.net> Date: Thu, 12 Dec 2002 13:46:53 -0500
Jim,
The script you posted, unfortunately, proves zip, since one can not cut and
paste it into Query Analyzer and execute it to demonstrate the alleged
problem.
You need to post a full repro script ... (simplified) table schemas (CREATE
TABLEs) and sample data (INSERTs) ... along with the code fragment to prove
a bug.
Perhaps more importantly, unless the code fails under SQL Server with SP2,
no one is going to log anything about it. It might have been already fixed
in SP2.
-------------------------------------------
BP Margolin
Please reply only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
can be cut and pasted into Query Analyzer is appreciated.
"Jim Barry" <jimbarry@adelphia.net> wrote in message
news:05b501c2a209$6c4f31d0$89f82ecf@TK2MSFTNGXA01...
> If this is validated, how do I sumbit the issue to MS?
- Next message: Kimberly L. Tripp: "Re: SQL Server 7 Service Account Name"
- Previous message: Russell Fields: "Re: Creating user after backup"
- In reply to: Jim Barry: "SQLServer 2000 SP 1 Bug"
- Next in thread: Jasper Smith: "SQLServer 2000 SP 1 Bug"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|