Tag Info

The following query will output the full contents of the current log in tabular format. If you only require a portion, replace the NULLs with LSNs. SELECT * FROM sys.fn_dblog(NULL,NULL) If th.e data is no longer in the log, then the following query will return the contents of your log backup. SELECT * FROM fn_dump_dblog (      NULL, NULL, 'DISK', 1, ...

There is possibility of fragmentation issue with the index. Check possibility of index fragmentation - Here is a simple query to check fragmentation on your existing indexes: DECLARE @DBNAME VARCHAR(130); SET @DBNAME = 'MYDBNAME'; DECLARE @DBID INT; SET @DBID = DB_ID(@DBNAME); SELECT OBJECT_ID AS objectID , index_id AS indexID , ...

Not sure how dbo is coming into play. Here is how you create a user in a database mapped to a server login, whether that login is already associated to a user in any other database: CREATE LOGIN foo WITH PASSWORD = 'bar', CHECK_POLICY = OFF; GO CREATE DATABASE splunge; GO USE splunge; GO CREATE USER foo FROM LOGIN [foo]; GO -- then permissions: GRANT ... TO ...

You can use the copy database wizard to move databases from one database instance to another. Right-click on an existing database, choose TASKS and then at very bottom, is 'Copy Database'. I would recommend the detach / re-attach database option, I don't like the other method, it's not reliable enough. You'll probably want to test a couple of database ...

Index Fragmentation and out of date statistics! Don't forget stats, it's one of the most important factors in SQL Server deciding whether or not to use a index. Next time it runs slow, check out how fragmented the clustered and non clustered indexes are, and also check to see if you have AUTO_UPDATE Stats enabled!

It could be that your index is no longer being used by the SQL Server query plan generator. This can happen for a number of reasons. A big reason could be the row count in your table. Have you generated a query plan in SSMS to see if the index is being used. And, if it is, whether a seek or scan is being done? A rebuilding of the index may or may not help. ...

Install a workgroup instance. Install any service packs / cumulative updates so that its @@version is >= the express instance. Backup the database from Express, restore it on the new Workgroup instance, take the database offline in Express, and point your application(s) at the new instance name (you'll need to update their connection strings). I believe ...