Index was outside the bounds of the Array. (Microsoft.SqlServer.smo)

Question

I am using SQL Server 2008 R2. It is working fine. But recently, I have changed my hosting server and I came to know that they have installed SQL Server 2012 on Server.

Now, Issue is that after connecting with Server Database through SQL Server 2008 R2, When I click on any table name or Stored Procedure, I am getting error : Index was outside the bounds of the array. (Microsoft.SqlServer.smo)

So, is there any issue from my side or It is from Server Side ??? and How can I prevent this issue ?

You can go ahead with it, new feature will not be available with it. — Samith C Valsalan, Mar 11 '15 at 09:36
In our case, we restored a 2008 R2 Database in SQL 2016 and we had the same problem trying to use the diagram in any way. After running SSMS 2016 13.0.15900.1 as administrator it solved the problem. Go figure! — Marc Roussel, Oct 19 '16 at 11:39

score 170 · Answer 1 · answered Sep 27 '16 at 11:48

170

Restarting the Management Studio worked for me.

answered Sep 27 '16 at 11:48

Abisoye Falabi

1,741
2
10
7

15

It seems the "out of bounds" error is caused by Studio caching the database structure. After you make enough changes to the structure, it will poorly match the cached version and start generating the error. Restarting rebuilds the cache. – David Austin Oct 17 '18 at 00:49
That was the real issue, i never had time to update my answer. Updating fixes the bug thou – Abisoye Falabi Oct 24 '18 at 16:58
1

I also had the same error with v18.6 version of SQL Server Management Studio (SSMS). The workaround is to exit the app and start again. – Jonathan Mendoza Oct 29 '20 at 01:43
1

I encountered this problem when I was using SQL Server Management Studio v.18, and closing the app and opening it again fixed the problem for me. – J. Zacka Dec 10 '20 at 00:51

score 54 · Accepted Answer · edited Aug 11 '14 at 07:03

54

Upgrade your SqlServer management studio from 2008 to 2012

Or Download the service packs of SqlServer Management Studio and update probably resolve you solution

You can download the SQL Server Management studio 2012 from below link

Microsoft® SQL Server® 2012 Express http://www.microsoft.com/en-us/download/details.aspx?id=29062

edited Aug 11 '14 at 07:03

Sandeep Kumar M

3,841
3
38
59

answered Apr 21 '14 at 17:45

Md.Rajibul Ahsan

853
7
8

2

There's not a fix for this yet. I have had this error in all versions of management studio including the 2018 - it's a shame this bug has been there for so many years now. – MeTitus Dec 31 '19 at 08:03
3

It is 2020 and it is still not fixed. – Antonín Lejsek Nov 05 '20 at 20:17
It is 2022 and it is still not fixed. – Brian Smith Jul 06 '22 at 00:56

score 52 · Answer 3 · answered Jan 23 '17 at 08:50

52

For me this problem still exists with SSMS version 2016 (13.0.16100.1).

A decent workaround is to not use the 'Right click' -> 'Add table...' dialog, but simply drag the table you want to add from the Object Explorer, onto the Diagram surface. While dragging the mouse icon changes into an 'add' symbol and the table is added when you release the mouse.

Beats having to close SSMS every time.

answered Jan 23 '17 at 08:50

MeanGreen

3,098
5
37
63

Diagrams are not available anymore v18.0 preview 4, hopefully they will be back soon! – MeanGreen Oct 19 '18 at 12:51
1

They are available again since 18.1 and up. Your wish has been granted (they were removed since 17.0 but back by popular demand it seems, see https://www.mssqltips.com/sqlservertip/6291/sql-server-database-diagram-index-was-outside-the-bounds-of-the-array/). – Abel Jan 19 '21 at 14:20

score 34 · Answer 4 · answered Jul 04 '17 at 22:12

34

Restarted worked! I found the same error to add new table to my database diagram on sql server 2016, restarted sql server management studio, finally solved.

answered Jul 04 '17 at 22:12

mernig

351
3
3

Yes. I had this error on SQL Server 2016 Management Studio (v 13.0.16106.4 ) All i had to do was restart the App / UI. Just disconnecting the Server and Reconnecting did not work. – joedotnot Dec 05 '18 at 06:41

score 8 · Answer 5 · answered Jan 05 '15 at 12:17

This is an issue if you are using 2008 management studio tools to connect to a SQL 2012 instance.

I experience this a lot if I am working on one server with SQL 2008, and trying to quickly query another server that is running SQL 2012.

I normally keep my personal workstation on the latest version of management studio (2012 in this case), and am able to administer all servers from there.

score 6 · Answer 6 · answered Feb 12 '15 at 07:11

6

The Reason behind the error message is that SQL couldn't show new features in your old SQL server version.

Please upgrade your client SQL version to same as your server Sql version

answered Feb 12 '15 at 07:11

Samith C Valsalan

139
1
5

score 3 · Answer 7 · answered Jul 21 '21 at 12:09

3

Solution: Ignore the error

Just to show that the error does not do much in SSMS version 18.9.2, drag the table to be shown in the diagram from the Object Explorer tab and wait for it to finish loading before you start using it.

answered Jul 21 '21 at 12:09

Chris Mutua

123
2
6

1

The user was using an old version of Management Studio. – mordack550 Jul 21 '21 at 15:02
This should be higher up, dragging a table/view to the designer, seems to clear this error. – J. Minjire Jan 17 '22 at 10:28

bielawski · Answer 8 · 2020-04-15T21:21:16.537

The suggested causes are now proven to be mostly impossible. I'm running SSMS V17.9.2 against SS 2014 and still have the problem. Memory problems have existed with this tool since at least 2006 when I started using SSMS.

Yes, MS 'wants' to get rid of diagramming but users won't let them. I have a feeling they will never fix any of these issues because they want users to be so fed up with the tool that enough of them quit using it and they can abandon it entirely.

Restarting is still a workaround if you can stand doing so numerous times per day.

score 1 · Answer 9 · answered Mar 15 '15 at 00:52

1

you must use new version of Management Studio. And also you will got an error 29506. so you should run as Administrator for setup. Look this site. http://shareis.com/post/29506-management-studio-express

answered Mar 15 '15 at 00:52

Çetin DOĞU

57
2

score 1 · Answer 10 · answered Dec 03 '15 at 09:44

I had a similar experience with using SMO via C# with the stack trace:

[1896] System.IndexOutOfRangeException: Index was outside the bounds of the array. 
[1896]    at Microsoft.SqlServer.Management.Smo.BitStorage.SetBit(Int32 itemIndex, BitIndex bitIndex, Boolean value) 
[1896]    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.AddObjectPropsFromDataReader(IDataReader reader, Boolean skipIfDirty, Int32 startColIdx, Int32 endColIdx) 
[1896]    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ImplInitialize(String[] fields, OrderBy[] orderby) 
[1896]    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.Initialize(Boolean allProperties) 
[1896]    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.OnPropertyMissing(String propname, Boolean useDefaultValue) 
[1896]    at Microsoft.SqlServer.Management.Smo.PropertyCollection.RetrieveProperty(Int32 index, Boolean useDefaultOnMissingValue) 
[1896]    at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName, Boolean throwOnNullValue, Boolean useDefaultOnMissingValue) 
[1896]    at Microsoft.SqlServer.Management.Smo.Information.get_MasterDBPath()

It turned out my versions of the CLR/NCLI/SMO were 10.50.1600.1. Upgrading them to 10.53.6000.34 fixed it - thus allowing the 2008R2 SMO to do many things with 2012 and 2014 servers.

Get them from the feature pack

https://www.microsoft.com/en-gb/download/details.aspx?id=44272

I found this link for SQL Server 2008 R2 Service Pack 3 to be clearer in terms of what installer to download https://support.microsoft.com/en-us/kb/2979597 — Justin, Apr 06 '16 at 14:30

score 0 · Answer 11 · answered Jun 20 '17 at 18:01

I found an issue with Diagram and Schema in SQL-Server 2016 that could be useful to the subject. I was editing diagram (related to, and with lot of tables of, the "sales" schema) and added a new table, BUT forgot to declare it schema, so it was with the default "dbo". Then when I returned to, and opened up, the schema "sales" and tried to add an existent table... Bluf! THAT Triggered exactly the same error described in that thread. I even tried the workaround (drag the table) but it didn't work. Suddenly I noticed that the schema was incorrect, I updated it, tried again, and Eureka! the problem was immediately away... Regards.

Welcome to [Stack Overflow](http://stackoverflow.com/) ! Please read [How do I write a good answer](http://stackoverflow.com/help/how-to-answer) ? — Saurabh Bhandari, Jun 21 '17 at 04:50

score 0 · Answer 12 · answered Aug 18 '19 at 13:59

0

It's very old problem with cashed content. MS planning to remove diagrams from SSMS, so they don't care about this. Anyway, solution exists.

Just close Diagrams tab and open it again. Works with SSMS 18.2.

answered Aug 18 '19 at 13:59

Tomas Vileikis

47
6

score 0 · Answer 13 · answered Nov 23 '20 at 11:24

0

You have to use latest version with SSMS

You can check latest builds via this page https://sqlserverbuilds.blogspot.com/

answered Nov 23 '20 at 11:24

Osman Taskiran

359
3
9

Welcome here @Osman Taskiran , can you please detail your post and explain the relation between SSMS (Management Studio) and the Question (as it is talking about indexes, etc.) – Useme Alehosaini Nov 23 '20 at 19:16

Index was outside the bounds of the Array. (Microsoft.SqlServer.smo)

13 Answers13

Solution: Ignore the error

Linked