Search Results

One approach that might help would be to specify the (few) columns you actually need instead of just using the "blanket" SELECT *..... When you define a small set of columns to retrieve, you might b …

Assuming you have a column of type DATE or DATETIME2 (or DATETIME), you can define two computed, persisted columns for year and month and put an unique index on those: ALTER TABLE dbo.YourTable ADD D …

There is no way to change the instance name without re-installing, sorry..... Update: OK, seems there are a few ways of doing this - not sure how well these work, though. I have not ever heard of any …

I don't think Sum is stored as a T-SQL function in your system that you could "peek" into. That's most likely code deep inside the SQL Server core. As a proof - you can e.g. get the body of other sys …

SQL Server does its own database file management - it does grow your .mdf file every time you need a few bytes more space. Instead, for each database file, you've defined an initial size and how it w …

Try this: select XRows.query('.') FROM @xml.nodes('/row') AS XTbl(XRows) WHERE XRows.value('(Id)[1]', 'int') = 1 This will return the entire <row> XML element as XML

A primary key on a INT IDENTITY ought to be very close to optimal, and as such should not lead to a significant index fragmentation. However: since your PK is (by default and unless you specifically …

That is expected and documented behavior: Dropping a database deletes the database from an instance of SQL Server and deletes the physical disk files used by the database. If the database or any o …

You could try this - if your MDF is intact (which according to your error message it doesn't seem to be.....): USE master GO CREATE DATABASE Test_Data ON PRIMARY (FILENAME = N'D:\Test_Data\Test_Da …

You can install multiple copies of SQL Server onto the same machine. To keep them apart, all "copies" (called instances) except the first (default) one have to be named. So by default, when you insta …

This will list all "most recent" restores for each database on your server: WITH LastRestores AS ( SELECT DatabaseName = [d].[name] , [d].[create_date] , [d].[compatibility_level] , [ …

You should be able to just deny permissions on the entire sys and information_schema schema as a whole: DENY SELECT On SCHEMA::sys To [user_name] DENY SELECT On SCHEMA::INFORMATION_SCHEMA To [user_na …