Is it possible to run: DBCC CHECKDB on a specific table in SQL Server 2005 database?
I have the following syntax:
DBCC CHECKDB
[
[ ( database_name | database_id | 0
[ , NOINDEX
| , { REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD } ]
) ]
[ WITH
{
[ ALL_ERRORMSGS ]
[ , EXTENDED_LOGICAL_CHECKS ]
[ , NO_INFOMSGS ]
[ , TABLOCK ]
[ , ESTIMATEONLY ]
[ , { PHYSICAL_ONLY | DATA_PURITY } ]
}
]
]
But keep getting incorrect syntax. I just want to run it to see what errors it throws up? Can you help me with writing the syntax? I want to remove all repair options.
DBCC CHECKDB as it names apply is for checking databases.
There is a DBCC CHECKTABLE command for checking specific tables. Usage is:
DBCC CHECKTABLE ('YourTable');
Late to the party, but, oh, well... See MS DBCC CHECKTABLE
Syntax:
DBCC CHECKTABLE ( table_name | view_name
[ , { NOINDEX | index_id }
|, { REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD } ] )
[ WITH
{ [ ALL_ERRORMSGS ]
[ , EXTENDED_LOGICAL_CHECKS ]
[ , NO_INFOMSGS ]
[ , TABLOCK ]
[ , ESTIMATEONLY ]
[ , { PHYSICAL_ONLY | DATA_PURITY } ]
[ , MAXDOP = number_of_processors ]
}
]
Be careful using any of the REPAIR options. Note that the ESTIMATEONLY Argument is just that and ZERO impact, and the PHYSICAL_ONLY option may have a much shorter run-time on large tables.
Related
Perhaps this is a pedantic distinction, but if we take the SQL grammar, in the following case from BigQuery:
query_statement:
query_expr
query_expr:
[ WITH [ RECURSIVE ] { non_recursive_cte | recursive_cte }[, ...] ]
{ select | ( query_expr ) | set_operation }
[ ORDER BY expression [{ ASC | DESC }] [, ...] ]
[ LIMIT count [ OFFSET skip_rows ] ]
select:
SELECT
[ { ALL | DISTINCT } ]
[ AS { STRUCT | VALUE } ]
select_list
[ FROM from_clause[, ...] ]
[ WHERE bool_expression ]
[ GROUP BY { expression [, ...] | ROLLUP ( expression [, ...] ) } ]
[ HAVING bool_expression ]
[ QUALIFY bool_expression ]
[ WINDOW window_clause ]
It is easy to see, for example, that the WHERE clause would be the section:
[ WHERE bool_expression ]
However, what is considere the "select clause". Is it the wrapper that contains everything? Or is it just the part that goes from SELECT up until the FROM section? Is there a way to distinguish the two?
For a specific example, how would the following be defined:
SELECT 1
FROM x
UNION ALL
SELECT 2
With the three components labeled with:
[ (full)
{ (SELECT until end or set/op)
< (SELECT until FROM):
[
{<SELECT 1> FROM x}
UNION ALL
{<SELECT 2>}
]
The SELECT statement is the whole statement from the word SELECT until the end.
The SELECT clause is from the word SELECT until the word FROM
I have a problem in understanding the Create Table syntax as shown in the MSDN.
I guess that [] means that sth is optional | - a different way - so
CREATE TABLE
[ database_name . [ schema_name ] . | schema_name . ] table_name
means that you can actually use:
1.CREATE table table_name
2.CREATE table database_name.schema_name.table_name
4.Create table database_name.table_name
3.Create table schema_name.table_name
but what about {} or ()
CREATE TABLE
[ database_name . [ schema_name ] . | schema_name . ] table_name
[ AS FileTable ]
( { <column_definition>
| <computed_column_definition>
| <column_set_definition>
| [ <table_constraint> ]
| [ <table_index> ]
[ ,...n ] }
[ PERIOD FOR SYSTEM_TIME ( system_start_time_column_name
, system_end_time_column_name ) ]
)
[ ON { partition_scheme_name ( partition_column_name )
| filegroup
| "default" } ]
[ { TEXTIMAGE_ON { filegroup | "default" } ]
[ FILESTREAM_ON { partition_scheme_name
| filegroup
| "default" } ]
[ WITH ( <table_option> [ ,...n ] ) ]
[ ; ]
?
First of all you should check Transact-SQL Syntax Conventions:
| (vertical bar) Separates syntax items enclosed in brackets or braces.
You can use only one of the items.
[ ] (brackets) Optional syntax items. Do not type the brackets.
{ } (braces) Required syntax items. Do not type the braces.
Now, as for creating table you could use:
CREATE TABLE table_name
CREATE TABLE database_name..table_name
CREATE TABLE database_name.schema_name.table_name
CREATE TABLE schema_name.table_name
So your Create table database_name.table_name is incorrect. You have to use the second example. When you pass .. the table will be created inside default schema (most likely dbo).
As for second question how to read MSDN documentation.
Probably the best way is visual way:
In the MSDN Library or the Technet website, Microsoft tend to use a pseudo syntax in explaining how to use T-SQL statements with all available options. Here is a sample taking from the Technet page on UPDATE STATISTICS :
UPDATE STATISTICS table_or_indexed_view_name
[
{
{ index_or_statistics__name }
| ( { index_or_statistics_name } [ ,...n ] )
}
]
[ WITH
[
FULLSCAN
| SAMPLE number { PERCENT | ROWS }
| RESAMPLE
| <update_stats_stream_option> [ ,...n ]
]
[ [ , ] [ ALL | COLUMNS | INDEX ]
[ [ , ] NORECOMPUTE ]
] ;
<update_stats_stream_option> ::=
[ STATS_STREAM = stats_stream ]
[ ROWCOUNT = numeric_constant ]
[ PAGECOUNT = numeric_contant ]
How to properly read such description and quickly figure out what is required and what is optional and a clean way to write your query?
You should refer to this Transact-SQL Syntax Conventions
The first table in that article explains pretty much everything.
In your example we can see the following:
UPDATE STATISTICS table_or_indexed_view_name
UPDATE STATISTICS is the keyword used
table_or_indexed_view_name is the name of the table or the view to update statistics for
[
{
{ index_or_statistics__name }
| ( { index_or_statistics_name } [ ,...n ] )
}
]
This is optional [], but if supplied, you have to put a statistic name {index_or_statistics__name}, or | a list of statistic names separated by commas { index_or_statistics_name } [ ,...n ]
[ WITH
[
FULLSCAN
| SAMPLE number { PERCENT | ROWS }
| RESAMPLE
| <update_stats_stream_option> [ ,...n ]
]
[ [ , ] [ ALL | COLUMNS | INDEX ]
[ [ , ] NORECOMPUTE ]
] ;
This is optional too []. If used then you must begin with a WITH and you have 4 options that you must choose from.
Your options are
FULLSCAN
SAMPLE number { PERCENT | ROWS }, where you have to define the number and you must choose from PERCENT or | ROWS
RESAMPLE
` [ ,...n ]' which is a list separated by commas
Then you have to choose either ALL, COLUMNS or INDEX and preside that with a comma if you have used the WITH.
Lastly you have another option to use the NORECOMPUTE and put a comma before it if you have used any other option before it.
<update_stats_stream_option> ::=
[ STATS_STREAM = stats_stream ]
[ ROWCOUNT = numeric_constant ]
[ PAGECOUNT = numeric_contant ]
These are the list of predefined options you may use where <update_stats_stream_option> is used before (in 4).
Any thing between Square Brackets [...] are Optional
Any thing seperated by the pipe | symbol is a one or the other option.
In your above example, you could read it as
UPDATE STATISTICS table_or_indexed_view_name
[ optionally specify an index as well]
[ optionally specify options using **WITH**
If you use WITH then you can follow it with one of the following keywords
FULLSCAN
OR SAMPLE number { PERCENT | ROWS }
OR RESAMPLE
].. and so on
create procedure test
BEGIN
select *
from User
END
;
Can someone tell me what is wrong in this and can you show me a simple create procedure?
The first link on google after typing "create procedure in sql server" gives your answer. Check out this:-
CREATE { PROC | PROCEDURE } [schema_name.] procedure_name [ ; number ]
[ { #parameter [ type_schema_name. ] data_type }
[ VARYING ] [ = default ] [ OUT | OUTPUT | [READONLY]
] [ ,...n ]
[ WITH <procedure_option> [ ,...n ] ]
[ FOR REPLICATION ]
AS { [ BEGIN ] sql_statement [;] [ ...n ] [ END ] }
[;]
<procedure_option> ::=
[ ENCRYPTION ]
[ RECOMPILE ]
[ EXECUTE AS Clause ]
If you're working with SQL Server, you've just missed AS:
create procedure test
as
BEGIN
select *
from User
END
DELIMITER $$
CREATE PROCEDURE `test`()
BEGIN
SELECT * FROM USER;
END$$
DELIMITER ;
EDIT: This is for Mysql..
crate procedure with parameter in SQL server
click here sqltutorialspoint
I'm trying to document some SQL and wanted to get the right terminology. If you write SQL like so;
select child.ID, parent.ID
from hierarchy child
inner join hierarchy parent
on child.parentId = parent.ID
Then you have one actual table ('hierarchy') which you are giving two names ('parent' and 'child') My question is about how you refer to the logical entity of a table with a name.
What would you write in the blank here for the name?
"This query uses one table (hierarchy) but two _ (child and parent)"
[edit] left a previous draft in the question. now corrected.
I believe this is called a SELF JOIN. A and B (or "child" and "parent", I think you have a typo in your question) are called ALIASes or TABLE ALIASes.
The concept is a self join. However, the a is a syntax error. The table is hierarchy, the alias is child.
I would call each part of a self join an instance.
In the SQL Server docs, the term is table_source :
Specifies a table, view, or derived table source, with or without an alias, to use in the Transact-SQL statement
In the BNF grammar, it's:
<table_source> ::=
{
table_or_view_name [ [ AS ] table_alias ] [ <tablesample_clause> ]
[ WITH ( < table_hint > [ [ , ]...n ] ) ]
| rowset_function [ [ AS ] table_alias ]
[ ( bulk_column_alias [ ,...n ] ) ]
| user_defined_function [ [ AS ] table_alias ] [ (column_alias [ ,...n ] ) ]
| OPENXML <openxml_clause>
| derived_table [ AS ] table_alias [ ( column_alias [ ,...n ] ) ]
| <joined_table>
| <pivoted_table>
| <unpivoted_table>
| #variable [ [ AS ] table_alias ]
| #variable.function_call ( expression [ ,...n ] ) [ [ AS ] table_alias ] [ (column_alias [ ,...n ] ) ]
'child', 'parent'
The term used in the SQL-92 Standard spec is "correlation name", being a type of "identifier".
'hierarchy'
The term used in the SQL-92 Standard spec is "table".
Hence the answer to your (edited) question is:
This query uses one table (hierarchy)
but two correlation names (child and
parent).