Firstly, if the recovery model of your database set to SIMPLE, then the answer is NO!

Secondly, do you have many transactions (inserts, update and deletes) against that database? If yes, then...

You need to understand that there are two types of collation - one has to do with Windows and the other is SQL Server.

When you first install SQL Server,...

A possible resolution to your problem is as follows:

declare @tbl table (lname sysname collate database_default)

insert into @tbl values ('ôyvind')

insert into @tbl values ('õyvind')

insert into @tbl values ('ôyvind')

insert into @tbl values ('õyvind')

insert into...

You will need to give the appropriate permissions to the SQL Server Agent service account. You can determine this by going to Enterprise Manager, open the 'Management' folder, right click...

By removing the BUILTIN\Administrators account from SQL Server, members of the [NT AUTHORITY\SYSTEM] workgroup account would no longer be able to access SQL Server unless explicitly granted. In other words,...

Try sp_spaceused

Are you able to change the ownership of the table (sp_changeobjectowner)? Ideally, tables should be owned by dbo, unless there is a good reason not to!

I think you may have the 'column result width' set to 14. Can you do the following select and see what it displays:

select 'qwertyuiuoipthe'

If it returns 'qwertyuiuoipth', then you will...

From BOL (Books On Line):

sp_droppullsubscription deletes the corresponding row in the MSreplication_subscriptions table and the corresponding Distributor Agent at the Subscriber.

If you are the owner of the database or a...

From your example above, are you building the select statement as dynamic SQL? Is the SQL part of a SP that is recompiling? On average how many records are returned? How is...

The required replication system stored procedure is: sp_scriptpublicationcustomprocs

You might also like to read this article in http://www.replicationanswers.com:

http://www.replicationanswers.com/NoSyncInitializations.asp

Unfortunately no Shahab! It was working fine, then failed for one day, and is now working again. Since my last post, there hasn't been any further issues.

The other thing...

The two documented role specific stored procedures are:

sp_helprole

sp_helprolemember

You can create indexes on a temp table as you would on a 'normal' table.

In your situation, try:

create clustered index CI__temp on #temp (Branch, StockCode)

You could also define a primary...

According to MSDN2 (http://msdn2.microsoft.com/en-us/library/ms187961.aspx), sp_executesql is listed under category [Database Engine Stored Procedures], whilst 'xp_' stored procedures are listed under [General Extended Stored Procedures]!