1: public void ExpandoObject()
2: {3: dynamic sampleObject = new System.Dynamic.ExpandoObject();
4: sampleObject.Test = "TestDynamic";
5: sampleObject.InvokeExpandoObject = new Action(() => Console.Write(sampleObject.Test));
6: sampleObject.InvokeExpandoObject.Invoke(); 7: }"...I recommend this article as is correct and presents a somewhat esoteric case of deadlock: the resource hash collision. The lock manager in SQL Server doesn’t know what it locks, it just locks ‘resources’..."
SbieDrv is Sandboxie's wedge. This one's existence makes sense, as well --- except, again, I get annoyed at programs that keep running after I've closed them. For fun, I wanted to see if I could unload it (since it wasn't running):C:\bin\si>fltmc unload SbieDrv
Unload failed with error: 0x801f0010Do not detach the filter from the volume at this time.
Huh; doesn't seem I can. Certainly there must be some performance penalty, to have every filesystem api call traverse a filter chain, no? Granted, altitudes decide just what they 'see', but, still... mightn't this be just one more drop in the bucket of what made Vista such a dog?
Moving on, to the last one, we've got FileInfo. This is simply bloat. It serves both ReadyBoost and Superfetch: both of which I've disabled. (This is a decent explanation of it: http://winprogger.com/?p=971)
Despite having them disabled, this filter is still loading, and, presumably, being referenced every time filesystem I/O occurs.
Naturally, I wanted to get rid of it, so, expecting it to behave, I bopped into regedit, and set the service start type to 4... and it still started... which admittedly had me scratching my head.
(DISCLAIMER: Following random advice on the Internet is BAD. Don't do this on your own system.)
So, I took the sledgehammer approach, and simply deleted the service key altogether... and it worked!
As I type this, I get the following Kirsten Dunst Turning Japanese (NSFW) warm and tingly feeling giving result:
C:\>fltmc
No filters loaded
Vunderbar! I can't say it feels faster, but I know my bits appreciate not being fondled quite as much; at least, that's what the voices in my head told me, when I was changing my tinfoil headgear.
Run REGEDIT.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\luafv change the "Start"=dword:00000004
00000004 is disabled, 2 is enabled.
Luafv.sys is a driver (system service) for UAC and not used for anything else. Once you disable UAC and stop this driver from loading you can reduce your start up load time..
After you've done this you will NEVER get any other messages asking your permission
...A lot has been written and discussed (and flamed) about UAC (aka LUA) but i’ll go over the basics one more time. There are a lot of applications that require the user to be an administrator on the machine for no good reason (the same way some online services ask for your home phone number or SSN.. you know they don’t really NEED it.. ). This used to be a pretty common thing a while back (I remember even IM applications that needed administrative privileges ?!) and the end result is that the machine is a lot less secure that it needs to be. So it is in some way related to security, but it’s not a security feature (though why the icon is a shield is beyond me.. MS must have had some leftover shield icons or something). Anyway, in order to ‘fix’ this without breaking backwards compatibility MS needed a couple of things...
The settings include:
- Setting up debugging boot configuration
- Configuring crash dump
- Disabling UAC, file and registry virtualization, and Shutdown Event Tracker
- Setting environment variables
- Configuring DbgPrint filters
BellaVista can do all of the above, with a minimal number of mouse clicks.
Here’s how an n+1 condition manifests itself:
- You query the database and get back a bunch of records in a table (this is one query)
- In your app code, you read through each record and refer to one or more attributes which need to be pulled from other tables
- Each record then causes the app to go off and make a heap of other queries in order to retrieve the attributes in the previous point (the n bit)
Building upon full text search, semantic search allows you to search not only for words, but also for the meaning (semantics) of these works. Mark Tabladillo, Ph.D., gave us great presentation at our Atlanta BI January meeting. He demoed how semantic search can be used to find the most common phrases in a document and how to find similar documents from a given search criteria.
USE msdbNow restart the SQL Agent
GO
EXEC msdb.dbo.sp_set_sqlagent_properties @errorlog_file=N'newpath\SQLAGENT.OUT'
GO
SELECT name, physical_name AS CurrentLocation, state_desc
FROM sys.master_files
WHERE database_id = DB_ID('master');
GO Important |
|---|
If the database cannot be started, that is it is in suspect mode or in an unrecovered state, only members of the sysadmin fixed role can move the file. |
NET START MSSQLSERVER /f /T3608
NET START MSSQL$instancename /f /T3608
ALTER DATABASE database_name MODIFY FILE( NAME = logical_name , FILENAME = 'new_path\os_file_name' )
SELECT name, physical_name AS CurrentLocation, state_desc FROM sys.master_files WHERE database_id = DB_ID(N'');
USE AdventureWorks2012;
GO
-- Find the average fragmentation percentage of all indexes
-- in the HumanResources.Employee table.
SELECT a.index_id, name, avg_fragmentation_in_percent
FROM sys.dm_db_index_physical_stats (DB_ID(N'AdventureWorks2012'), OBJECT_ID(N'HumanResources.Employee'), NULL, NULL, NULL) AS a
JOIN sys.indexes AS b ON a.object_id = b.object_id AND a.index_id = b.index_id;
GO
-- create database on physical drive c:\ with default setting CREATE DATABASE [TestPerformance] ON PRIMARY ( NAME = N'TestPerformance', FILENAME = N'TestPerformance.mdf' , SIZE = 4352KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) LOG ON ( NAME = N'TestPerformance_log', FILENAME = N'TestPerformance_log.LDF' , SIZE = 576KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) GO -- create database on ramdisk (drive L:\) with default setting CREATE DATABASE [TestPerformanceRamdisk] ON PRIMARY ( NAME = N'TestPerformanceRamdisk', FILENAME = N'TestPerformanceRamdisk.mdf' , SIZE = 4096KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) LOG ON ( NAME = N'TestPerformanceRamdisk_log', FILENAME = N'TestPerformanceRamdisk_log.ldf' , SIZE = 1024KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) GO -- create simple test tables in both databases CREATE TABLE TestPerformance..TestInsert (testColumn UNIQUEIDENTIFIER) GO CREATE TABLE TestPerformanceRamDisk..TestInsert (testColumn UNIQUEIDENTIFIER) GO -- run this script on both databases and compare time DECLARE @i INT = 100000 DECLARE @start DATETIME = GETDATE() DECLARE @end DATETIME WHILE @i > 0 BEGIN INSERT INTO TestInsert VALUES (NEWID()) SET @i -= 1 END SET @end = GETDATE() SELECT CONVERT (TIME, @end - @start)
It doesn’t take too long to set up a tool to monitor a file or directory – you can download FileMon from:The Connect to Server dialog can pop up in different situations where there is no security context for the connection to use. If you use registered servers (and save the password there) when you view the registered servers, select a server in the Registered Servers task pane and then click New Query on the toolbar or Right Click, Connect, Object Explorer or New Query which will result in connecting under the security context you used when registering the server. If a server isn’t selected, there is no security context available so the Connect to Server dialog pops up. I haven’t heard of passwords being “lost” or “forgotten” using the registered servers task pane and saving registration information there.
SELECT
name AS FileName,
size*1.0/128 AS FileSizeinMB,
CASE max_size
WHEN 0 THEN 'Autogrowth is off.'
WHEN -1 THEN 'Autogrowth is on.'
ELSE 'Log file will grow to a maximum size of 2 TB.'
END,
growth AS 'GrowthValue',
'GrowthIncrement' =
CASE
WHEN growth = 0 THEN 'Size is fixed and will not grow.'
WHEN growth > 0 AND is_percent_growth = 0
THEN 'Growth value is in 8-KB pages.'
ELSE 'Growth value is a percentage.'
END
FROM tempdb.sys.database_files;
If the SQL instance fails to start as a service, it can be started in a command-prompt window. Generally, this is only done for troubleshooting purposes. (See http://msdn.microsoft.com/en-us/library/ms180965(v=SQL.100).aspx) For example, if a SQL instance starting up as a service cannot find the storage device that the tempdb files are to be stored on, the instance will fail startup. Since the service cannot be started, its tempdb location also cannot be reconfigured in the normal way. In this case, the solution is to run the instance in a command-prompt window, reconfigure the tempdb location, stop the command-prompt instance, and start it again, running as a service. To start a SQL instance in a command-prompt window, cd to the instance's Binn directory (eg. 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL_INSTANCE\MSSQL\Binn'), and enter the following command:sqlservr -f -s "SQL_INSTANCE" This command runs the SQL instance named "SQL_INSTANCE" inside the command-prompt window itself, with a minimal configuration. A minimal configuration limits instance execution to a single user.To reconfigure the tempdb file locations, open another command-prompt window and use one of the SQLCMD.EXE methods shown above. When finished, return to the command-prompt window in which SQL is running, type Ctrl-C, and confirm the shutdown request. Afterward, run the SQL instance as a service. |
| Using SQLCMD.EXE | To change the location using the command-line tool SQLCMD.EXE, open a command-prompt window with Administrator privileges, and cd to the instance's Binn directory. Then follow one of the three methods shown below:
| ||||||||||||
First Method: Scripted | Create the two script files, 'ChangeLocation.sql' and 'ReportLocation.sql', with the content shown in the tables above. Modify the file path specification appropriately. To execute the scripts, open a command prompt and enter the commands shown below:
| ||||||||||||
Second Method: Interactive | Execute the commands in an interactive SQLCMD session, as shown below (modify the file path specification appropriately):
| ||||||||||||
| Third Method: Command-Line Query | The query commands can be concatenated for use in a single argument on the command line, as shown below (modify the file path specification appropriately):
|
| Using "SQL Server Management Studio" |
| |||||||||||||
| QUERY TO CHANGE FILE LOCATION (ChangeLocation.sql) |
| USE master go ALTER DATABASE tempdb MODIFY FILE (NAME = tempdev, FILENAME = 'R:\temp\tempdb.mdf') go ALTER DATABASE tempdb MODIFY FILE (NAME = templog, FILENAME = 'R:\temp\templog.ldf') go |
| QUERY TO REPORT FILE LOCATION (MyReportScript.sql) |
| SELECT name, physical_name FROM sys.master_files WHERE database_id = DB_ID('tempdb') go |