98

The accepted answer is valid for previous version of Sitecore, but it does not reset the password salt and doesn't in fact reset the password to 'b'. In order to do this, you need the following script (which also will unlock the admin user if locked): UPDATE [aspnet_Membership] SET [Password]='qOvF8m8F2IcWMvfOBjJYHmfLABc=', [PasswordSalt]='...


56

Yes there is. Switch to your core database and execute the SQL below to reset the password to b: UPDATE [aspnet_Membership] SET Password='qOvF8m8F2IcWMvfOBjJYHmfLABc=' WHERE UserId IN (SELECT UserId FROM [aspnet_Users] WHERE UserName = 'sitecore\Admin') Alternatively navigate to /sitecore/admin/unlock_admin.aspx and click Unlock Administrator. For this ...


24

In a Sitecore 8, this will: Cleanup CyclicDependences (items that couldn't be removed by CleanupOrphans because they have a parent but are not in the item tree) Cleanup InvalidLanguageData (remove all data from items in languages that are not defined as a valid language in the Sitecore system) Cleanup Fields (delete data from fields -SharedFields, ...


23

Unlock_Admin doesn't work when you will decide to change your password encryption from SHA1 into SHA512 (regarding to Sitecore recommendations). It does NOT reset password for Sitecore admin - it just unlock the Sitecore account - as the name of method says. Here you have got a code of this method: public override bool UnlockUser(string username) { this....


21

A very large log file is symptomatic of the problem of no backups taking place. Under normal circumstances SQL log files get truncated on backup. It is quite normal that a CI environment gets quite many updates, and if your SQL is running in "Full" mode, this will grow your transaction log. I would propose setting it to "simple". It will be slightly ...


17

1) Infrastructure MongoDB will introduce new element into infrastructure of your solution. This increases cost of servers, cost of maintenance and at the end complicates the overall solution landscape. In scaled solution you would need couple of Mongo DB server e.g. replica sets to support failover, redundancy and data availability. If you stay with MS ...


15

Scenario Let's say you need create a second publishing target called staging. Steps Publishing Target You need to create an item for the new database in the content tree at the path /sitecore/system/Publishing targets. Then in the field Target Database, you enter the name like staging. Database Now, you need also to create a new database. You can just ...


12

Right after post my question, realized that sqlcmd was not installed at the server - which is weird, because XP1 topology didn't require at all! In my case, I had to download and install Microsoft ODBC Driver 13 for SQL Server Microsoft Command Line Utilities 13 for SQL Server Once I got both installed, it was just a matter to re-run the XP0.


12

There are a few options to transfer Users and Roles from one instance to another. Sitecore Packages You can use the standard Package Designer application from the Development Tools menu in the Sitecore Desktop. You can then add the Roles and Users that you would like to package up for migration, generate the package, download it and then install it on the ...


11

Ok. Well. Would definitely be possible to set something up with Unicorn for this - albeit it a highly unusual configuration. Steps I would take would look something like this: Set up Unicorn on the CM box to serialize all of the web content you want to regularly push across to CD This will ensure, the file system always has a copy of everything that is ...


11

Yes, you definitely still need to perform regular database maintenance. Especially on Sitecore DBs like Analytics that have a lot of activity and develop index fragmentation quickly. At least, if you want to maintain performance of your site. I should mention, that whitepaper was written a long time ago, and Azure gets updates every month. A number of the ...


11

Typically, a cleanup operation will remove data in invalid languages and items in orphaned trees. That means: all invalid language data (i.e. data for which the language does not exist) will be removed; all field data for non-existing items will be removed; orphaned items from the database will be removed; all caches will be cleared. Update : This code ...


9

The Analytics DB is used as a reporting database for xDB. MongoDB is the collection database and periodically this is aggregated and stored in the Analytics db (also called the reporting db). If you have xDB and Tracking disabled, then you will not need the Analytics DB. IF you are using xDB and want to be able to view all the reports etc... then you will ...


8

Yes. You need a new <appender>. First you need to set up a table to receive the logging information: CREATE TABLE [dbo].[Log] ( [Id] [int] IDENTITY (1, 1) NOT NULL, [Date] [datetime] NOT NULL, [Thread] [varchar] (255) NOT NULL, [Level] [varchar] (50) NOT NULL, [Logger] [varchar] (255) NOT NULL, [Message] [varchar] (4000) NOT ...


8

I am not aware any IOPS guidelines, but there is a Sitecore Experience Platform 8.2 Performance White Paper where they have made many test and the Premium Storage Account is only mentioned for MongoDB. In general, your Primary MongoDB takes the biggest hit and needs the fastest drives. Other than that, Sitecore solutions have largely been found to be CPU ...


8

As you mentioned Replication is required for some Sitecore databases, but SQL Azure (PaaS) does not support SQL read-write geo-replication currently just read-only(https://docs.microsoft.com/en-us/azure/sql-database/sql-database-designing-cloud-solutions-for-disaster-recovery), so the only option is to have all CD locations connect to the central Core ...


7

You are right, you granted to much privileges. You don't have to assign any server roles, but you should should assign db_datawriter, dbreader and public role memberships for your user to the web and master databases. You should also assing execute permissions on all the stored procedures for your db user. for the core database, assign the following role ...


7

To be honest, I'm not sure if what I describe below will fix the ASYNC_NETWORK_IO issue. Seeing NETWORK_IO lets me think that the issue is more network or server related than being a real Sitecore issue. However, we have also seen high loads due to EventQueue table activity. With the help of Sitecore Support we've come to this solution: Clean EventQueue on ...


7

That would be an XM environment. You require: forms, core, web and master https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/sitecore_on_azure/deploying/sitecore_configurations_and_topology_for_azure#_XMSingle


6

The Sitecore 6.6 scaling guide has this to say about the IDTable: You can store persistent mappings of arbitrary keys to Sitecore IDs in the Sitecore IDTable. By default, this is only used by the Sitecore CMS WebDAV functionality to keep locks on media items in the CM environment and does not need to be synchronized with the CD environment. You ...


6

After having processed an event from the queue each instance updates the associated last processing timestamp (LPT) which is stored in the Properties table and has the key in the following format 'EQStamp_{Sitecore-Instance-Name}' Therefore, you can use the LPT to filter out events which have already been processed by a given instance - literally just the ...


6

Thank you, Vinicius. To add to the correct answer, after downloading the two utilities from your answer, my problem was not resolved. I encountered into the same issue when running Sitecore installation using SIF on staging environment where SQL server was not added to environment variables. When running the SIF on dev/staging/prod environments where SQL ...


6

Yes You can add as many databases as you like. I have an admittedly very old tutorial that takes you through the steps. Having just skimmed through it, I would say it's probably still perfectly valid - as Sitecore's Data Provider model hasn't changed significantly in a decade. Working with multiple content databases in Sitecore 6 But if you want to go on ...


5

You've seen the "Optimize SQL Server Performance" section (Not Applicable to Azure SQL) at https://doc.sitecore.net/sitecore_experience_platform/setting_up__maintaining/xdb/session_state/walkthrough_configure_a_shared_session_state_database_using_the_sql_server_provider as it relates to Session state? While no silver bullet, that approach can improve ...


5

Just adding to Richard Seal's answer that you can rebuild the contents of the SQL reporting database, as documented here. As the documentation notes: The Sitecore Experience Database (xDB) uses two database systems (SQL Server and MongoDB) that need to be kept in sync to provide accurate data for Sitecore reporting applications: MongoDB collection database ...


5

In order to be 100% sure that a particular event was processed by all servers, you would need to write a rather complex query. To illustrate, I've written a query to return all events processed by a single web server: SELECT * FROM [EventQueue] where [Stamp] <= ( select Cast(CONVERT(nvarchar(100), [Value]) as int) from [Properties] where [Key] = ...


5

You might take a look at the new Vault product from XCentium. They do some really interesting things with moving content between environments using Git. Not sure whether your network restrictions would be prohibitive but might be an option.


5

It depends how you've set up your database. You can set the recovery model to simple to get rid of most of the log file content. Go to the database with SQL Management Studio, right click on the database and select properties. In the popup, select the Options tab and change the recovery model accordingly. Alternatively, you can do this with a SQL command as ...


5

There's no formula, because the workload is as much a function of your code as it is about the number of concurrent users. If you are using caching properly an S will be sufficient for "web" but not "master". If you have a logged-in area you will load up "core" as well. My suggestion is to start with S3 for master and web, and monitor the DTU, CPU, IO and ...


5

Using DotPeek, I have spotted the issue in the class Sitecore.Cloud.Packaging.WebDeployPackages.WebDeployPackageBuilder on the Build method, I suspect this is the root cause of the problem. { "core", path1 + "\\Sitecore.Core.dacpac" }, { "master", path1 + "\\Sitecore.Master.dacpac" }, { "...


Only top voted, non community-wiki answers of a minimum length are eligible