[MS-SQL] DB의 모든 테이블 정보

select OBJECT_NAME(id)


, rows

from sysindexes

where indid = 1

order by rows desc

댓글

댓글 쓰기

이 블로그의 인기 게시물

Visual Studio 2017 MSBuild Setting

Publish Profile xml version = "1.0" encoding = "utf-8" ?> < Project ToolsVersion = "4.0" xmlns = "http://schemas.microsoft.com/developer/msbuild/2003" > < Target Name = "AddGulpOutput" > < ItemGroup > < _CustomFiles Include = "lib\**\*" /> < FilesForPackagingFromProject Include = "%(_CustomFiles.Identity)" > < DestinationRelativePath > lib\%(RecursiveDir)%(Filename)%(Extension) </ DestinationRelativePath > </ FilesForPackagingFromProject > </ ItemGroup > </ Target > < PropertyGroup > < WebPublishMethod > FileSystem </ WebPublishMethod > < PublishProvider > FileSystem </ PublishProvider > < LastUsedBuildConfiguration > Release </ LastUsedBuildConfiguration > < LastUsedPlatform > Any CPU </ LastUs...
자세한 내용 보기

Difference between Classic mode and Integrated mode in IIS

Classic mode (the only mode in IIS6 and below) is a mode where IIS only works with ISAPI extensions and ISAPI filters directly. In fact, in this mode, ASP.NET is just an ISAPI extension (aspnet_isapi.dll) and an ISAPI filter (aspnet_filter.dll). IIS just treats ASP.NET as an external plugin implemented in ISAPI and works with it like a black box (and only when it's needs to give out the request to ASP.NET). In this mode, ASP.NET is not much different from PHP or other technologies for IIS. Integrated mode, on the other hand, is a new mode in IIS7 where IIS pipeline is tightly integrated (i.e. is just the same) as ASP.NET request pipeline. ASP.NET can see every request it wants to and manipulate things along the way. ASP.NET is no longer treated as an external plugin. It's completely blended and integrated in IIS. In this mode, ASP.NET HttpModules basically have nearly as much power as an ISAPI filter would have had and ASP.NET HttpHandlers can have nearly equivalent capabilit...
자세한 내용 보기