iPad meets the Rural Lifestyler.

Like quite a number of IT professionals in the Bay of Plenty, NZ, I have bought into the dream of having an intense IT career and...

New plan, post changes hereto attached.

Thanks ALZDBA - this guided me into a number of areas to tweak a validate.

USERNAME - I created a computed field to create a SimpleUserName (sometimes it was fully qualified...

Thanks Craig - MAXDOP did resolve the Parallelism issue. Performance did tweak a bit.

Execution plans have been attached.

Have tweaked the code to parse the csv string of usernames to a tmp table to see if things would go better by removing some of...

I fully understand this whole situation. This is all part of the "beauty" and "pain" of a capitalist society - not to say it is a bad thing - it...

This is great - despite the limitations on accuracy.

I have a collection of IP Addresses in the Visitor_Log table, which I convert to an IPNum - no problems there -...

I found a similar post in another forum which gave me some guidance to getting this "potentially" sorted.

http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/9ea9343b-6dac-4fcb-bde2-4cdcf4862daa

1.I stopped SQL Server Agent on my Distribution server in order to effectively...

Did you get anywhere with this?

I have a SQL2005 - SQL2008 replication giving me similar grief.

Someone told me to try this but I haven't been able to prove it yet, due to a problem I am having, but it might help you:

select

cast(count(*) as varchar(20))...

michael.wiles (5/29/2008)

---

I am trying to fine tune an application in VB that access SQL Server 2005. After reviewing the SQL Profiler log there seems to be an excessive amount...

That fixed it!

Had to add a DATETIME2 field, copy the data from the original field, remove indexes that referred to the orig, delete the orig field, rename the new field...

Thanks - I will give that a go.

In which case, I have lots of tables in this DB that need the datatype DATETIME to be upgraded - just as well...

The data tyep is a [datetime], as it was in SQL2005 - I take it that [datetime2] is now the equivalent in SQL2008?

No - not a varchar(8) but it passes a varchar (any size, usually 27), specifically this value '2009-11-30 15:16:43.9270000' and that's when SQL2008 gives the error "Error converting data type...