Books on line says "A parsed document is stored in the internal cache of SQL Server 2000. The MSXML parser uses one-eighth the total memory available for SQL Server. To...

I use snapshots when I need to duplicate a live environment for testing purposes.

1. Receive change request.

2. Snapshot the live to a development machine.

3. Test on the development machine.

4. Make...

Oh the embarrassment, thanks to Carsten Dauguaard for spotting it.

exec sp_xml_preparedocument @iDocumentHandle OUTPUT, @stdoc

should be

exec sp_xml_preparedocument @iDocumentHandle OUTPUT, @stXML

Oh the embarrassment!!!!

Thanks to Carsten Dauguaard for spotting it.

In the code for the stored procedure

exec sp_xml_preparedocument @iDocumentHandle OUTPUT, @stdoc

should be

exec sp_xml_preparedocument @iDocumentHandle OUTPUT, @stXML

This is what you get when you...

If these critical fixes are not part of SP3 then would you recommend holding off on SP3 and wait for SP4?

What are you going to do with that text parameter after you have retrieved it?

Why not loop through the returned recordset and build up the string in your app and...

I DO name my constraints.

If SQL needs an index and there isn't one available it creates its own.

Sometimes an index is not appropriate but SQL may decide that it needs...

If all you want is a list of names simply run

SELECT Name FROM SysObjects WHERE TYPE='P'

P = Stored Procs

V = Views

TR = Triggers

If you want the actual definitions then try

SELECT...

I'm willing to be that the dbo user does not have an associated login.

Use sp_ChangeDbOwner '<<whatever login you want>>' within the database and the dbo user should be fine.

I often...

Although these utilities are useful I felt a chill go down my back the first time I saw one of these things working.

I used the toolkit from http://www.lostpasswords.com on NT...

I had a table called Tbl_CommenceDownload and noticed that I gained an index called tTbl_CommenceDownload.

I attempted to drop this and got the standard message that tells you that you are...

I thought this at first, however it is not as simple as the naming convention.

Not all system indices start __WA etc.

The way I get around it at present is to...

I started off with SQL 6.5 when Enterprise Manager was given the euphenism Enterprise Mangler therefore we always used TRANSACT SQL and explicitly named every constraint.

SQL also creates system indices...

Sorry about the lateness of this post.

I've found that @@ROWCOUNT gets its knickers in a twist with triggers.

INSERT DestinationTable(Fields)

SELECT Source.Fields

FROM SourceTable

WHERE Some Clause

SELECT @@ROWCOUNT

If DestinationTable has a trigger then @@ROWCOUNT...

On a related subject, should Int IDENTITY columns be deprecated infavour of GUID columns?