I'm lucky in that i'm both developer and DBA as well. (primarilly DBA tho)

i think the problem lies in the mentality difference between developers and DBA's

if you think of the...

what account run the replication on the subscriber (if it's pull) or publisher (if it's push) - does this account have permission to use this.

i'm guessing that your account...

SalesLineItem: (itemCode, quantity)

where is the reference to saleID

perhaps

SalesLineItem: (ID(PK),saleid(FK),itemCode(FK), quantity,)

just a thought

customers are an entity

Sales: (saleId,, customerID, amount, storied, saleBalance,

Customer: (customerID,mobileNo,CustomerName)

the following is the section from books online:

basically the system that worked in 2000 should work in 2005 as it's implemented by e-mail - the problem we're having is that...

so the pager alerts in 2005 aren't the same as the email pager alerts in 2000?

i've just had the same problems on a new install - i think it relates to the priveleges of the SERVICE ACCOUNT - not your login account.

I usually resort to one of the following

pig headed stubborness

obfuscating database code

boring them to death (ok - that's not hard)

or my favourite so far has been in sql 2005 -...

run the following

select name from sysobjects where name like '%mytable%'

you should see a list of all the constraints in there somewhere. the create statement will have defaulted it to...

select table1.*,table2.* from table1 inner join table2 on table1.site_ref=table2.site_ref

the problem we're seeing with 2003 is not a network issue, it's a casae of outlook 2003 jsut not behaving the way 2000 used to.

the problem is really evident when...

i've seen this behaviour on betweens before.

try using where Ticks.Tick_Price = @Triggered_Price AND

Ticks.Tick_DateTime >= @Triggered_Datetime AND

Ticks.Tick_DateTime<=(dateadd......

no idea why it fixed the problem but it did - possibley something to do...

we have a similar problem in that a few of our outlook 2003 installations take a long time to initialise. this causes sql agent to hang.

interestingly enough - these 2003...

this really depends on your table structure

if you have an id column in the table (as primary key) then it's pretty easy

basically your first query returns the top 1 record

the...

just one i made up to demo the principal

you need to order the results in some sort of order to be able to effectively say this is the 101st record...