I've done this quite a few times before in other packages. WHY is it telling me that rowValues(1) is out of bounds?? I've commented out EVERYTHING in my script, except for these 2 rows. If I comment out Row.col2, I don't get the out of bounds error. If I include Row.col2, I get the out of bounds error, so it doesn't like rowValues(1).
The file has 13 columns in it. A row looks like this:
"ATMC","004930202",529.000000,"L",11.380000,6020.020000,7210.270000,6072.920000,"BSZTX","MTPO",,"Equities","My Fund Appreciation","06/30/2006"
Currently underway with migrating from SQL 2005 to SQL2012. I have loaded all of my SSRS reports into Visual Studio 2010 (SQL Server Data Tools) and they all appeared to upgrade fine. I have 150+ reports and I'm in the middle of recreating a tonne of Subscriptions.
However, I have 4 reports that run fine, execute nicely.... but as soon as I click on 'Subscriptions' I get the index bounds array error.
I could attempt to re-create them. It's only 4 reports after all. But it doesn't answer the question, why would the reports execute fine, but unable to create a subscription?
I got rid of the .rdl.data files, which apparently has been a successful fix for this problem in the past. Everything worked fine Thursday when I left (I was off Friday - Saturday), but today I get this error for all but one of the reports in the solution when I try to preview the report. BTW, the published stuff works fine. Thanks in advance for any help.
Index was outside the bounds of the array When working with a SQL Server 2005 database and ASP.NET, I get this error when trying to pull a small amount of data from the database, Any help would be great, thanks a lot I work for a large company, so I have to watch the code I release.
On the data tab in reporting services I have just named the stored procedure I wish to run. This Stored procedure expects a datetime parameter. When I select run in the data tab and enter the date (I have tried various different formats) the error "Index was outside the bounds of the array. (system data)". Does anyone know how this can be solved? it seems a simple issue but is turning into a pain to sort out.
When I go to SQL 2012 through SSMS 2005, I get the message Index outside the bounds of array. Will it fix if I install SSMS 2012? Do I need to remove SSMS 2005?
I need to setup log shipping from a 2008 Standard to a 2012 Standard server. I have not found any restrictions for this, however, when I want to connect to the 2012 server on the add secondary server page, I receive the following error:'Index was outside the bounds of the array. (Microsoft.SqlServer.Smo)'.
I am getting this error "Index was outside the bounds of the array. (Microsoft.SQLServer.Smo)"..I have downloaded a hotfix, but when I tried running the patch, I was told the expected version is 10.2.4000.0, I am running 10.0.1600.22.I can not locate the correct patch for my version.
Microsoft SQL Server Management Studio 10.0.1600.22 ((SQL_PreRelease).080709-1414 ) Microsoft Data Access Components (MDAC) 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft MSXML 3.0 6.0Â Microsoft Internet Explorer 9.11.9600.17041 Microsoft .NET Framework 2.0.50727.5485 Operating System 6.1.7601
I am getting an intermittent problem with executing queries on my workstation. Whenever I execute a couple of store procedures that return a large numbers of rows (200,000 to 500,000 rows) I receive an intermittent error message when running the same sp with the same parameters sometimes the procedure runs fine and returns the result, sometimes I get an error message
Error message is: Index was outside the bounds of the array.
Sometimes
Error message is: Internal connection fatal error.
Sometimes I get a datetime overflow
I also occasionally get these intermittent messages when I execute the native query that the SP wraps.
I have SSMS 2015 SP1 installed on my workstation, the servers are a range of server from 2008 R2 SP2 to 2014 SP1. It feels like a client problem as there are applications connecting to these servers and running the stored procedures without issue...
If I delete 5 or more columns from a table I get the error "Index was outside the bounds of the array", OK is the only response. I then have to close the report and then open it again.
Easy fix is don't delete more than 5 columns, but my template is setup with 15 columns as it's far quicker to delete them as it is to add them 1 by 1 each time. I've finally got around to looking for a hotfix or something similar but can find no mention of this exact error relating to table column deleting.
Anyone else experience this or know if there is a hotfix for it?
I have a database that is growing by 40 to 50 megs a day. I understand that the '_W' objects are statisical information for query performance and not indexes, but does anybody know how much disk space is actually used by these objects. I do have the 'auto create statistics' and 'auto update statistics' set on.
please explain the differences btween this logical & phisicall operations that we can see therir graphical icons in execution plan tab in Management Studio
URGENT!!!!! I am getting this error and cannot find out what is happening anywhere!!!
Server: Msg 7319, Level 16, State 1, Line 3 OLE DB provider 'SQLOLEDB' returned a 'NON-CLUSTERED and NOT INTEGRATED' index 'account_index' with bookmark ordinal 0.
I have a SQL 2000 database. The table's primary key is set up as a "regular" index and another field is set up as a clustered index. When attempting to delete the index on this other field, I am receiving the following error message:
'tblQuestionAnswer' table - Unable to delete index 'tblQuestionAnswer1'. ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]A column has been specified more than once in the order by list. Columns in the order by list must be unique.
I do not understand why I am receiving this message in relation to the deletion of an index. Any ideas?
'PXQ_2' table - Unable to delete index 'PK_PXQ'. ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000102e000 in file 'D:MSSQL2000MSSQLxxx.mdf'.
I can't drop Primary Key. How to fix this problem?
Guys, We just got an Error 644 on our DB, the error was:
Could not find the index entry for RID '169bc61301c3950000209e1a0002000000030000' in index page (1:1683508), index ID 0, database 'TR'..
Error: 644, Severity: 21, State: 3
We run dbcc CheckDB on the TR DB with no error:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'TR'.
I read JohnSharp post, and tried the script from Paul:
DBCC CHECKTABLE (sysindexes) WITH NO_INFOMSGS, ALL_ERRORMSGS
it return no erros as well, anyone got any more info on whats this error is?
At the time of this happen, its seems that a process is running, which run some stored proc which will create some temp tables, will that message be relating to some index that created on the tempdb (from the temp tables) rather then the index on the TR DB? Since we can't even tell which table its affected, is there any way to find out?
Any assistance with this issue would be greatly appreciated. TIA!
Server: DBServer-1 Task Detail: Reorganize index on Local server connection Databases: dbA,dbB,dbC,dbD,dbE,master,model,msdb
Object: Tables and views Compact large objects Error No: -1073548784 Error Message: Executing the query "ALTER INDEX [PK_Residential] ON [dbo].[Residential] REORGANIZE WITH ( LOB_COMPACTION = ON )" failed with the following error: "A severe error occurred on the current command. The results, if any, should be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Windows Server 2003 Standard Edition w/ SP2 SQL Server 2005 Standard Edition (9.0.3054)
I get the following error message while droping unique index.
Server: Msg 3723, Level 16, State 5, Line 1 An explicit DROP INDEX is not allowed on index 'dbo.ALEG.IX_ALEG'. It is being used for UNIQUE KEY constraint enforcement.
When I try to run the ITW to increase performance I get this error in the event viewer. Earlier I have used the ITW with success but now I dont get any more index recommendations, just this error. Do you know what it means :
"The description for Event ID ( 4 ) in Source ( ITW ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error in Parsing Event: execute sp_Sys'.
A few days ago a sproc stopped working, only noticed it this morning, when checking information to see what's up I get this:
Server: Msg 644, Level 21, State 1, Procedure uspV2InventoryFetch, Line 83 Could not find the index entry for RID '45574f44523738313834202020202020202020202020202020202020202020' in index page (1:11690152), index ID 2, database 'ASOS'.
Connection Broken
I've treid DBCC CHECKDBing all related tables and everything else. Even tried dbreindexing a couple of them too, everything reports as correct. When I looked further at the problem I spotted "index ID 2" in there, on checking this out in sysindexes it seems that the name field of sysindexes where id = 2 is SYSINDEXES and TSYSINDEXES.
I can't seem to do a DBB DBRECINDEX against a system table.
I build some t-sql code to check if full text is installed on the sql server. If not, some sql statements must be not executed. Here is my code:
if (select serverproperty('IsFullTextInstalled')) = 1
Begin
EXEC sp_fulltext_database 'enable'
CREATE FULLTEXT CATALOG [...] WITH ACCENT_SENSITIVITY = OFF AS DEFAULT
CREATE FULLTEXT INDEX ON dbo.Test (Name LANGUAGE 0, Description LANGUAGE 0) KEY INDEX IX_Test_1 ON [...] WITH CHANGE_TRACKING AUTO ALTER FULLTEXT INDEX ON dbo.Test ENABLE
End
Statement 1 and 2 is not executed, but for statement 3 the server throws the following error: Full-Text Search is not installed, or a full-text component cannot be loaded.
I don't know why the server tries to execute statement 3, because it is in an if statement.
I'm testing db to db transactional replication on a box ( all on the same box ) and the distribution agent fails with the above error. I know it's something to do with the physical server as this test works on other servers fine. SQL2k Ent sp4 on w2k3 ent sp1. ( clustered )
Server and Agent accounts are in local admins, tried push and pull, named and anonymous. Replication also fails if I use the default snapshot location. I suspect policy restrictions ( maybe on the sql service accounts ) Any pointers would be helpful - there are no errors other than above, sadly.
I'm getting the following error on our merge contents table in one of our DBs:
Msg 8952, Level 16, State 1, Line 1 Table error: Database 'ks241', index 'MSmerge_contents.nc3MSmerge_contents' (ID 1950682047) (index ID 3). Extra or invalid key for the keys: Msg 8956, Level 16, State 1, Line 1 Index row (1:1893:42) with values (partchangegen = NULL and tablenick = 17665001 and rowguid = AEAE7256-F571-478E-B2B4-D142B47C38C1) points to the data row identified by (). Msg 8952, Level 16, State 1, Line 1 Table error: Database 'ks241', index 'MSmerge_contents.nc3MSmerge_contents' (ID 1950682047) (index ID 3). Extra or invalid key for the keys: Msg 8956, Level 16, State 1, Line 1 Index row (1:1893:66) with values (partchangegen = NULL and tablenick = 17665001 and rowguid = B94F1591-33B0-4625-A269-DB9B8B05BCCE) points to the data row identified by (). CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'MSmerge_contents' (object ID 1950682047). repair_fast is the minimum repair level for the errors found by DBCC CHECKTABLE (ks241.dbo.MSmerge_contents ).
There are no other corruption issues on the server that I can find. I do not believe there are any current hardware issues, though I am not on site.
What would be the best way to resolve this? Is recreating or defrag/rebuild the index an option, here? Or can I just run a repair on this? Since it's a merge table, I'm a little gun shy, having limited experience with replication.
Thanks.
____________________________________________________________________________________ "Believe in those who are seeking the truth. Doubt those who say they have found it." -Andre Gide
I have a problem with multiple databases on a server. I originally read another post that went into detail on this same error. After reading the post I decided to re-index the table to see if that would fix my issue. I started on Saturday by re-indexing a table on database 'a' - the process completed after that; I received another error on database 'b' on Monday i subsequently re-indexed all indexes on this database; today I have received the same message on database 'c' and 'd'. All post that I have read seem to point to an issue with only one database and not multiple databases. I have approximately 100 databases on this cluster - SQL 2000. The physical server logs only error shown is '000009ac.00001744::2007/12/29-15:12:58.848 ERR [CP] CppReadCheckpoint unable to copy file U:Disk12Partition1d61e68e-a60f-4ca6-b9ae-df3b893e4bb2 0000001.CPT to C:DOCUME~1mscsLOCALS~1TempCLS302F.tmp, error 3 000009ac.00001744::2007/12/29-15:12:58.848 ERR [CP] CppReadCheckpoint - Was that due to quorum resource not being up ??? ' before corruption of database 'a'.
Here is the entire error if you think it will help. The error has been the same on all databases: 12/28/2007 6:23 AM A possible database consistency problem has been detected on database ‘ substituted_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database 'substituted_name'..
When I run the DBCC CHECKDB command I got these errors on Substite name database: DBCC results for 'FVD_A'. Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 165575628, Index ID 2. Keys out of order on page (1:12743984), slots 97 and 98. There are 72920059 rows in 2281375 pages for object 'FVD_A'. CHECKDB found 0 allocation errors and 1 consistency errors in table 'FVD_A' (object ID 165575628). DBCC results for 'FVD_CVS322'. Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 181575685, Index ID 2. Keys out of order on page (1:7250519), slots 30 and 31.
I am at a loss. I believe we may have a bigger issue, but the SAN Administrator and Server Admin are saying there is nothing they can do. Do I have a true SQL Server issue or something else.
[OLE/DB provider returned message: There is no catalog. ] OLE DB error trace [OLE/DB Provider 'MSIDXS' ICommandText::Execute returned 0x8004181d]. Msg 7320, Level 16, State 2, Line 1Could not execute query against OLE DB provider 'MSIDXS'.
this is the query where BookPDF is a link index server.
Code Snippet
select * from articles INNER JOIN
((SELECT Articles_id as XID,FTBL.Rank from Articles inner join OpenQuery(BookPDF,'select rank,filename from scope('' "" '') where contains(contents,'' legal '')') as FTBL on Articles.[book_pdf] like '%' + FTBL.[filename] ) Union (SELECT Articles_id as XID,Keytbl.rank from Articles inner join Containstable(Articles,*,'legal') as KEYTBL on Articles.Articles_id = KEYTBL.[Key] )) as XTBL on Articles.Articles_id = XTBL.XID where (newsletter_name NOT IN(select Newsletters_id from Newsletters where Product IN (23,24)) AND (dont_show_in_search = 0 )) order by issue_date desc
We are currently attempting to (Merge) replicate a database between 2 servers; distributor and subscriber. Apparently there are no Primary Keys in the database, and without the input of the developers, we can only assume that data integrity must be maintained by the application and the database is somewhat generic. In any case, what we are experiencing is that when we attempt to replicate, and you may know, you need PKs. Without any, SQL Server has utilized it's own (Row GUIDs). The Snapshot worked fine, but the merge agent reports error 1505.
The error is "CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID %d. Most significant primary key is '%S_KEY'."
The fix and workaround are SP2 and deselecting Unique in the index propoerties of the index raising the error. We already had SP2 on the system. Tried the other and still the same issue occurs.
Microsoft's Knowledgebase has nothing. Any suggestions or fixes would be greatly appreciated.
I am unable to migrate any DTS packages, from a SQL Server 2000 package, from a structured storage file, or from a DTS package imported into SQL2005 (Developer Edition, 32 bit). Running the Package Migration Wizard, every time I get to the List Package screen, i get the error below. I haven't found any other mention of this so far. Anyone else seen this error or have suggestions?
First of all, sorry for the cross post but i need a quick answer on this.
I am executing a CLR Stored Procedure from a Windows Mobile device and regularly get a general network error.
The stored procedure cycles through up to 70 tables, checking for any records between two dates. The LastUpdate field is in each one of the 70 tables and is indexed.
The mobile device regularly reports general network error, which is due to a timeout. Command timeout is now set to 10 minutes but the timeout still occurs.
The stored procedure appears to get stuck on a particular table. If I rebuild the index on this table, it will get past it but then get stuck on the next table.
I set up a maintenance plan to run every 5 minutes (extreme, I know!) but the indices would appear to corrupt (without any activity on the table) in less than this interval.
However, running the exact same query from SQL Server Management Studio works correctly every time and usually within 10 seconds.
I€™m sure that it has something to do with the indices but cannot seem to resolve the issue. It€™s even more confusing how only the mobile device is affected!
i have created a fact table which has unique cluster index as below,
CREATE UNIQUE CLUSTERED INDEX [FactSales_SalesID] ON [dbo].[FactSales] (salesid ASC) WITH (DATA_COMPRESSION = PAGE) GO however later when i add CLUSTERED COLUMNSTORE INDEXES : CREATE CLUSTERED COLUMNSTORE INDEX CSI_FactSales ON dbo.FactSales WITH (DATA_COMPRESSION = COLUMNSTORE) GO
it prompts error.
Msg 35372, Level 16, State 3, Line 167 You cannot create more than one clustered index on table 'dbo.FactSales'. Consider creating a new clustered index using 'with (drop_existing = on)' option.
