I do not think you can do this. One nice thing about FOR XML is that it produces well-formed XML . Having an &...

This is indeed weird. Dropping a table that has a foreign key referencing itself is allowed, and there should not be a warning. Only foreign keys from other tables are...

The very first thing probably is to run SQL Server 2005 Upgrade Advisor. It detects a lot of things such as using new reserved keywords (e.g. pivot).

Regards,

...

Once you are using ntext, text and image columns there is no real limit to their combined lengths. Each of them can be about .5GB, 1GB, 1GB respectively. They are...

Hi Michelle,

OPENROWSET accepts only string literals as the filepath, so you would need to construct this query dynamically, something like:

CREATE PROC insertBulk
    ( @filename NVARCHAR(260)
  ...

Which table are you deleting from?

The delete statement has two from clauses. The first one specifies the table you are deleting from, the second is for the conditions. You can...

If the data is over 8K, and you want to store it in the db, then text and ntext can work for you. Jeff is right however, that it is...

Identity columns are really good as primary keys. They are small, and keeping an index small results in faster searches. However, whether identity columns should be part of the clustered...

sp_permissions is not a system stored procedure shipped by MS. However an updated version of it you can find on: http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=251338

Regards,

Andras

You could use dynamic SQL like:

DECLARE @query NVARCHAR(4000)

SET @query = 'Select * From ' + @server + '.DB1.dbo.Table1 '

EXECUTE ( @query )

Regards,

Andras

Your only choice is to use BLOBS. These are the text, ntext and image datatypes. For text it is ntext and text. See http://msdn2.microsoft.com/en-us/library/aa174534(SQL.80).aspx

Regards,

Andras

Wow, I really like it , Thanks Peter.

One small note about it: it seems to require 'Ad Hoc Distributed Queries' to be set, which...

You will need to shrink the tempdb manually.

dbcc shrinkdatabase (tempdb, 'target percent')

Andras

I've just found an article by Andy Warren that may be useful (the result is the same)

http://www.sqlservercentral.com/columnists/awarren/profilerloggingresultstoatable.asp

Regards,

Andras

Ken,

As far as I know with sp_trace_create you cannot write to a table directly. One way around it is if you write to a file, stop the trace using sp_trace_setstatus,...