Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
ADS Version: ads-windows-x64-14.0.0-beta-32
Operating Environment: Windows 8 64 bit.
Database:SQLServer 2000.
Connect to SQLServer 2000,Go to User tables under Model database -> Right Click Create table->Click on Schema drop down->you will see that Schema drop down will have only one schema name i.e "dbo",other schema names are missing.So we can create table under one schema only.But by using Query analyzer we can create table in others schema as well.So schema drop down should have others schema as well.
In SQLServer 2005 we have other schema in drop down list.
|
|
96 KB
|
|
526 KB
This is tricky as sql server changed from 7 to 2000 to 2005. I have changed up the queries that extract the schemas for 2000 and 2000 only to better extract using the <database>.dbo.sysusers table where the name is not public. This will match the schemas <database>.dbo.sysschemas table that was introduced in 2005. This change should be tested intensively as it touches the schema list extracted from connectionmetadata for sql server 2000 in all areas.
Verified on ads-windows-x64-14.0.0-beta-42 Build
Verified on ads-windows-x64-14.0.0-beta-42 Build
Issue #9409 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
1 issue link |
is a duplicate of #9549
Issue #9549SQL Server - why do I see more schemas in v14 using same connection from v13? |
This is tricky as sql server changed from 7 to 2000 to 2005. I have changed up the queries that extract the schemas for 2000 and 2000 only to better extract using the <database>.dbo.sysusers table where the name is not public. This will match the schemas <database>.dbo.sysschemas table that was introduced in 2005. This change should be tested intensively as it touches the schema list extracted from connectionmetadata for sql server 2000 in all areas.