I have a SQL 2005 server that has my iMIS database. Unfortunately, iMIS requires that the compatibility mode of SQL be set to 80 (SQL 2000). I'm trying to use the function asi_SplitString in my code, but I get an error when I call it telling me to change the compatibility level to 90 (not supported by iMIS). I want to use the function so that I can easily search the multi-instance field setup in an iMIS demographics table.

I’ve added a page to IC for recording details of release schedules for software used by iMIS – for example the next versions of Microsoft SQL Server or Microsoft Office.

http://www.imiscommunity.com/microsoft_and_other_vendor_software_release...

If you come across any information on release schedules for products that we use or integrate with can you update it here.

Passing this exam gives you MCTS – SQL Server 2005 certification. It’s a prerequisite for the MCITP: DBAdmin cert, but it’s not an elective for MCPD (unlike the 70-229 SQL 2000 exam for MCSD).

The Transcender test is available on DEVEXAM, and it’s helpful. It includes simulations that work like the ones on the actual test. I also used the ExamCram book by Thomas Moore, which had good test-specific material. I’ll pass it on to Mark D. for the Dev library.

Problem Description
I have a problem with iBO.COM inserts in SQL 2005 on an Australian server.

We have a live and a test site, with respective databases.

The live site is showing this in the SQL trace when iBODataServer user connects. Inserts work.

- network protocol: TCP/IP
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on

There is a continuing need for a SQL Function or equivalent to decrypt credit card information from iMIS.

Of course there is an overall security concern, but there still are frequent requirements by customers to have a method to decrypt credit card info, beyond the standard reporting in iMIS.

I have done a little research on this. There is just a little info on it in www.imiscommunity.com.

I just came across a pretty useful script to automatically version control the schema of a SQL Server database.

I think the idea is you can schedule it to run and it will automatically version control differences in the schema.

Unfortunately it only works for VSS, rather than TFS, but perhaps there is an equivalent/similar object model for TFS?

The attached file comes from http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1093178,00.h...

I attended a presentation on SQL Server 2008 in Cambridge last night. I'm sure the list of features are available elsewhere so I will just add some comments on things of interest.

The presenter was Dr Andras Belokosztolszki - one of the SQL gurus at Red Gate. This was part of a series of presentations being given by NxtGenUG - coming up are:

Media Centre
ADO.NET data services
F# (presented by the Don Syme - guy who invented it)

We have been attempting an install on brand new Windows 2003 64bit server and are getting an "Unable to connect to server." error - we have been working with Tech support and ruled out a few things but still nothing... In the process we have reinstalled SQL 2005 SP2. We have done this install on a Virtual Server configured as closely as we could (32bit) to the actual server and had no problems... But the Actual Server install keeps failing. I see there have been some issues on a 64bit install - will follow up on some of those but we can't even get the installer to finish running.

I encountered this when installing SQL Server on a new Vista machine. The full error is:

SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.

Someone asked me about this the other day and I thought I would post the code here as the answer isn't obvious.

This is the problem:

declare @seqn int
EXEC @seqn = sp_asi_GetCounter 'Relationship'

This doesn't work - the counter value isn't set in the @seqn variable - it will just be zero.

To get this to work, use this code:

declare @seqn int
-- EXEC @seqn = sp_asi_GetCounter 'Relationship'