I'm seeing the same thing but I have over 34,000 of these messages for tempdb.

I would use this where I only want to update non 'sa' owners.

SELECT 'ALTER AUTHORIZATION ON DATABASE::' + QUOTENAME(name) + ' TO [sa];'

FROM sys.databases

WHERE...

Hi

You just replace the given contents for a new script task, with the contents given in the article and just replace your file locations and details.

Regards

Carolyn

There is a SQl Server user group in Manchester try going to this.

http://sqlserverfaq.com/events/595/Introducing-SQL-Server-with-Martin-Bell-and-Chris-TestaONeill-Bring-a-Friend-Wednesday-night-Meeting-at-Swinton-Insurance.aspx

I'd ask about the stored procedure, what is it doing? Is there a simple select or is it a cursor. what is the table definition. You just havn't presented enough...

If you had one job that looked at a table to pick the list of databases to backup, you could use this to manage the fact that you only...

I'd normally bring the file in as all text fields not caring about the format then running sql against the data for format or format in a view/procedure and load...

Try:

DECLARE @xml xml, @v-2 nvarchar(max)

SELECT @v-2 = N'A # B # C'

SET @xml = N'<root><r>' + replace(@v,'#','</r><r>') + '</r></root>'

SELECT

replace(a.value('.','varchar(2)'),' ','') AS [RowName]

FROM @xml.nodes('//root/r')...

The BCP Syntax

bcp {[[database_name.][owner].]{table_name | view_name} | "query"}

{in | out | queryout | format} data_file

[-m max_errors] [-f format_file] [-e err_file]

...

Did you run the script against the master database rather than running it against the required database by any chance? Try running again against the required database.

I prefer a strong but most importantly honest manager, and one that does not have a 'tefal' (non sticky) attitude. A person who stands up to be counted, and takes...

Probably a bit late to reply but the message: [SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL is just a warning and if you...

I've not seen this before but Googled it and it seems that this is by design. The data source for reports with dynamic connection functionality needs to be local...

I think there may be something wrong with the syntax of the connection string your using, can you post it here?

If you're smart you'll make use of the new slipstream features and integrate the Service Pack and\or Cumulative Update to decrease the time taken to deploy your new SQL Server...