Viewing 15 posts - 61 through 75 (of 159 total)
You simply have to supply the schema name when referencing the object:
myschema.TheTable
yourschema.TheTable
if I use schemaname.tablename, system wll show "Incorrect syntax near '.'." as the picture
Instead of...
March 22, 2021 at 12:56 pm
thank you Johan Bijnens!
but some databases are still SQL server 2008.
March 3, 2021 at 1:53 am
Thanks, I know we can get some informations about foreign key Thru below statement.
SELECT OBJECT_NAME(FK.referenced_object_id) AS 'Referenced Table',
OBJECT_NAME(FK.parent_object_id) AS 'Referring Table',
FK.name AS 'Foreign Key',
COL_NAME(FK.referenced_object_id, FKC.referenced_column_id) AS 'Referenced Column',
COL_NAME(FK.parent_object_id, FKC.parent_column_id) AS...
December 10, 2020 at 1:48 am
You have a hypothetical index in the list on the right. It isn't a real index Google search the following: MS SQL Server hypothetical indexes
ok,I'll google what the MS...
December 9, 2020 at 4:26 am
sorry, my sql server is 2008 R2
December 9, 2020 at 1:48 am
1. Not generally available. If an index was created by adding a PRIMARY KEY constraint, sys.objects would have the create time of that index.
2. Yes. For example: SELECT t.name...
December 9, 2020 at 1:38 am
This may get you some of what you want.
SELECT
SS.name SchemaName,
ST.name TableName,
ISNULL(SI.name, '') IndexName,
SI.type_desc IndexType,
IUS.user_updates,
IUS.user_seeks,
IUS.user_scans,
IUS.user_lookups,
SSI.rowcnt,
SSI.rowmodctr,
IUS.last_user_seek,
IUS.last_user_scan,...
December 9, 2020 at 1:01 am
Ant-Green , Thank you for your kind help!
December 8, 2020 at 9:14 am
well noted, thank you Ant-Green!
December 8, 2020 at 3:43 am
The things you mention don't typically cause the crazy increase you speak of. And I just told you a "good way" to find it so someone can...
December 1, 2020 at 1:11 am
The things you mention don't typically cause the crazy increase you speak of. And I just told you a "good way" to find it so someone can fix it....
November 30, 2020 at 2:49 am
Crazy increases in size are normally due to a query that has one or more "accidental Cross Joins" in the form of "Many-to-Many" results. They typically contain a DISTINCT...
November 30, 2020 at 12:53 am
For best overall performance, it's extremely likely that you need to change the clustering index on the table to be ( OrderID, ItemID ). Especially if the table is...
November 27, 2020 at 6:31 am
I think I can help with that one.
IDX1 would have the 3 columns with the data ordered by OrderID, then ItemID, and finally Status. If there were more columns...
November 27, 2020 at 4:51 am
Yes, you can drop IDX1; IDX12 can cover all queries that would use IDX1.
thank you !
if I create the following on the table , could you please tell the...
November 26, 2020 at 12:38 pm
Viewing 15 posts - 61 through 75 (of 159 total)