Drenlin

That was what I was fearing, manually entering each record. I hope I have the power of delegation or someone else has a tip. Thanks Steve for quick responses.

Sorry, let me be clearer. Yes, they are trusted logins (AD accounts) to the old domain and the old domain will be scrapped for the purpose of the school (not completely scrapped as it is owned by the local authority but the school will not longer have access). The connect.ini has the 'trustedauto' in it. I imagine the users will want to continue to use trusted logins (what user is happy to have another login to perform) therefore the new logins need to be linked to the new domain accounts. Jon Update: I have read the Sysman manual and it covers setting up Trusted logins and reverting back to SQL but not a change of domain.

Morning all. Wondering if there is someone out there with experience of SIMS Trusted Logins who can offer advice. My experience on trusted logins is limited. I am about to perform a SIMS migration but we are changing from a Local Authority domain to a Multi Academy domain. The SIMS migration is no trouble for me, having done many over the 15 years supporting the technical aspect of SIMS but I do not know what I would need to do regarding the logins. The old domain will not be accessible after the migration so I cannot setup a trust. Is there something I should do before the migration? Is there anything to aid the integration to the new domain? I tried searching the forum but could not locate anything about migrations with Trusted Logins. Thanks in advance

An older article but simpler to understand if you need a basic guideline. Still relevant for SQL 2012/2014 https://sqlserverperformance.wordpress.com/2009/10/29/suggested-max-memory-settings-for-sql-server-20052008/

On the server we on only get a screen "How do you want to open this type of file". Close the question.

You can get your head in a twist if you take on all the advice out there but please remember the size of the database involved. You are not talking about multi terabyte databases. Advice I hear but get confused about is the advice to seperate log data files, log files and the tempdb to seperate disks for performance. But surely this would need seperate RAIDs to get that performance or do you still get it if they are on logical drives on the same RAID? I have not worked that one out yet. What we do implement though is to size your data file for the space it requires with 1 years growth. Also, check your autogrowth rate for the data and log file. Often the default for SIMS (due to the default Model database) is 1Mb growth for data and 10% for log file. Each year, perform a growth again. This cuts down on fragmentation (which can cause a performance hit). Set the data growth to a good size chunk to catch the missed expected growth. As for the log file, look up the topic of 'virtual log files'. This is what your SQL log file is made up from. Too many and this will slow the performance. If you do not set your log file initial size and growth correctly, each time you run the Capita reindex patch you are encouraging a large number of virtual log files.

Only for looking at the manuals. It doesn't stop you performing tasks. Uninstall Adobe Reader after the client installation. It is only installed as part of the SIMSInfrastructureSetup so it doesn't reappear after an upgrade.

Even on our hosted servers we do not get constant 100% CPU when a couple of schools are perfoming changes to academic year (but it does slow down). I guess it is one of those things that cannot be directly tracked but we prefer not to have Adobe load each time we enter a database post upgrade.

Don't blame you for being suspicious considering the number of updates on a normal workstation. You got me checking our SIMS hosted servers. Server 2008 did not have Reader installed. Server 2012 server have Adobe Reader but no update manager. May have to uninstall the reader.

Never forget the golden rule. Hold the camera you are planning to buy, never buy just from others saying it is good. If you do not like the feel of the camera (weight, shape, location of the buttons/wheels) then this will put you off using the camera. Years ago I used to have a Canon EOS600 (yes, non digital version) and it was a lovely camera. When I went to digital SLR (Canon stuff had long gone) I went with the Nikon D90 which felt wonderful. The Canons didn't feel right in my hands.

I confirm what sonofsanta said. If you have lenses that are usable on a digital body, stick to the brand. If you don't then you should look at the lens prices as well. Chances are that you will be buying one other lens to fill your needs (unless you find someone selling all you need for the right price).

Not speaking from experience but the post I mentioned indicated all Discover machines will get messages saying Discover is being deployed/upgraded if you redeploy Discover. Not something I would want to see. Hopefully this will be looked into.

Have you looked at the SIMS forums? See the thread called 'SOLUS 3 issues for Capita to address' by Richard Chappelle and the answer will be in point 4 of his first post. Not a good answer though. You may want to change your Discover deployments to a scripted install from the MSI (See the Discover Commandline Install - ref 21914) then add them to Solus3

Capita have just informed me that this will be fixed in the Autumn 2013 Release.

We are all waiting for the latest installable release which can be used for installing from scratch. I imagine documentation will be on that. This is a yearly ISO release that was due in May. We are guessing the delay is due to the SQL 2012 Migration. Why release an installed that uses the old version of SQL.

With the following query in SQL Management Studio against the SIMS database (although I cannot confirm this also works with Solus3 patches). select patch_id, date_applied, description from sims.db_update_log where successful = 'T' You then add to the end how you want it sorted: order by patch_id if you are looking for a specific patch order by date_applied if you want to see patches by date order add DESC at the end of the order by command to reverse the order. D'Oh! was 2 minutes too slow.