What I was saying was that

SELECT TOP 1000000

IDENTITY(int,1,1) AS number

INTO dbo.Numbers

FROM master.dbo.syscolumns sc1,

...

But that's not going to give you what you said you want. I'm debugging this in my head but if both strings have 10 digits then the "select" is going...

Just to help you out for your specific case:

create table Numbers (Number int)

go

insertintoNumbers values (1)

insertintoNumbers values (2)

insertintoNumbers values (3)

insertintoNumbers values (4)

insertintoNumbers values (5)

insertintoNumbers values (6)

insertintoNumbers values (7)

insertintoNumbers values (8)

insertintoNumbers values...

Here's a solution, I think. Functions aren't the most efficient things around so if your table is large performance may suffer. Just create the function below and then run your...

Check the value of the Query Timeout parameter in your Distribution Agent profile. You probably need to increase it significantly. If you are using the Default profile you will need...

Glad to be of assistance.

Mike

James,

Sorry. I've never used clustering so if you don't mind I'll chicken out and not even take a stab at an answer!

Mike

Can't believe the rubbish I wrote first time. You need to put the SELECT inside the stored procedure. A temporary table is only visible to its creator and only exists...

A little more information required really. One of the usual problems here is that a large table can cause the bulk copy to exceed the timeout value in the profile....

You can do all the rebooting you want without fear of losing any data. We have scheduled reboots for most of our publishers and distributors (publishers and distributors run on...

You can have any number of subscribers as far as I am aware. However, you're correct to think about performance implications as each replication agent has an overhead which I...

On the server which houses your distribution database you will see a Distribution cleanup job. This is what is responsible for marking your subscriptions as inactive. If you have undistributed...

If you can remove replication and put it back on that would be the correct solution given the situation you find yourself in. That way you know everything is clean...

Well, I've never tried it and I'm not quite sure why anyone would want to do it but I'm sure you have a good reason.

sp_update_job will allow you to rename...

I'm feeling a little uneasy now. Might I respectfully suggest that if you are this new to SQL Server and you are going to be writing SQL to interact with...