Problem with Index Tuning Wizard

Hi,
Before using the ITW, you should get a load of the queries
you are running. You can capture the events in profiler
and then use that load file for the ITW to use.
hth
DeeJay
>--Original Message--
>When running the Index Tuning Wizard (ITW) on our SQL
Server we got a
>error message : 'Could not complete cursor operation
because the table
>schema changed after the cursor was declared'
>The ITW was used only to advice new indexes. I know that
it creates
>hypothetical indexes in the sysindexes table, but what
are the changes
>in the user-tables ?
>How do you use the ITW without interfering with the real
>schema-definitions ?
>thanks,
>Robbert
>.
>
I know how to use the ITW. The problem is the tuning part. According to
the error-message, the ITW makes changes. What are these changes and why
are they interfering?
Robbert
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
sql

Problem with Index Tuning Wizard

When running the Index Tuning Wizard (ITW) on our SQL Server we got a
error message : 'Could not complete cursor operation because the table
schema changed after the cursor was declared'
The ITW was used only to advice new indexes. I know that it creates
hypothetical indexes in the sysindexes table, but what are the changes
in the user-tables ?
How do you use the ITW without interfering with the real
schema-definitions ?
thanks,
RobbertHi,
Before using the ITW, you should get a load of the queries
you are running. You can capture the events in profiler
and then use that load file for the ITW to use.
hth
DeeJay
>--Original Message--
>When running the Index Tuning Wizard (ITW) on our SQL
Server we got a
>error message : 'Could not complete cursor operation
because the table
>schema changed after the cursor was declared'
>The ITW was used only to advice new indexes. I know that
it creates
>hypothetical indexes in the sysindexes table, but what
are the changes
>in the user-tables ?
>How do you use the ITW without interfering with the real
>schema-definitions ?
>thanks,
>Robbert
>.
>|||My theory on this is while you were running the ITW
someone in your tream made a change to the structure a
table, which caused it to get an error.
I have run ITW a number of times using our Production
Database, with no problems.
Peter
"We are all worms. But I believe that I am a glow-worm."
Winston Churchill
>--Original Message--
>When running the Index Tuning Wizard (ITW) on our SQL
Server we got a
>error message : 'Could not complete cursor operation
because the table
>schema changed after the cursor was declared'
>The ITW was used only to advice new indexes. I know that
it creates
>hypothetical indexes in the sysindexes table, but what
are the changes
>in the user-tables ?
>How do you use the ITW without interfering with the real
>schema-definitions ?
>thanks,
>Robbert
>.
>

Problem with Index Tuning Wizard

Hi,
Before using the ITW, you should get a load of the queries
you are running. You can capture the events in profiler
and then use that load file for the ITW to use.
hth
DeeJay
>--Original Message--
>When running the Index Tuning Wizard (ITW) on our SQL
Server we got a
>error message : 'Could not complete cursor operation
because the table
>schema changed after the cursor was declared'
>The ITW was used only to advice new indexes. I know that
it creates
>hypothetical indexes in the sysindexes table, but what
are the changes
>in the user-tables ?
>How do you use the ITW without interfering with the real
>schema-definitions ?
>thanks,
>Robbert
>.
>I know how to use the ITW. The problem is the tuning part. According to
the error-message, the ITW makes changes. What are these changes and why
are they interfering?
Robbert
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Problem with DTSX

I am trying to execute an DTSX for Exporting data from SQL 2005 to Access Database. From SQL Wizard, the Export process is running fine.

When I tried to execute the same using an Stored Procedure (
XP_CMDShell 'dtexec /F E:\Shared\Export\Export_Fame_Entity.dtsx') it is getting executed for long time.. but never gets completed and thus, not giving any error also.

Help required.........

regards,
Ravi K
Mascon Global Limited

In SQL Server 2005 the xp_cmdshell is disabled in new installations. This may be your problem. The Books Online topic, Surface Area Configuration for Features, rovides more information about enabling xp_cmdshell.

Also it looks like your command line is missing quotes. Try using "E:\Shared\Export\Export_Fame_Entity.dtsx"
I ran a package successfully from the Query window in SQL Server Management Studio using the following syntax
xp_cmdshell 'dtexec /f "C:\UpsertData.dtsx"'
The SQL Server 2005 Books Online topic, dtexec Utility, provides a wealth of information about running packages by using dtexec.

Marianne
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.

Problem with distributor

In the replication wizard, the first menu "SELECT DISTRIBUTOR", have two
options
a) Make the "Myserver" its own distribuitor, SQl Server will create a
distribuiton database server and log.
b) Use the following Server, ( The selected server must already be
configured as Distribuitor).
When i select the first option pop-ups a window with this text :
"SQL Server Agent on SERVER1\Macuco" currently uses the system account ,
which causes replication between servers to fail, In the following dialog
Box, specy another account for the service startup account "
In the SQL Server Agent Properties which account i need to choose?
Thanks in ADvance
Alejandro Carnero
Brazil-Santos
Ideally use a local admin account.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"alecarnero" <alecarnero@.uol.com.br> wrote in message
news:OTGvbxcAGHA.740@.TK2MSFTNGP12.phx.gbl...
> In the replication wizard, the first menu "SELECT DISTRIBUTOR", have two
> options
> a) Make the "Myserver" its own distribuitor, SQl Server will create a
> distribuiton database server and log.
> b) Use the following Server, ( The selected server must already be
> configured as Distribuitor).
> When i select the first option pop-ups a window with this text :
> "SQL Server Agent on SERVER1\Macuco" currently uses the system account ,
> which causes replication between servers to fail, In the following dialog
> Box, specy another account for the service startup account "
> In the SQL Server Agent Properties which account i need to choose?
> Thanks in ADvance
> Alejandro Carnero
> Brazil-Santos
>

Problem with decimal point

I have got txt file and I am trying to import this file into the database. For that action I use SQL Server Import and Export Wizard. I use Locale Czech and CodePage 1250. In the text file is the column in that format: 18152.65 - it is number with decimal point. When I use BCP utility for importing data, I use datatype decimal(10,2) and everything is OK. But when I try to use Import and Export Wizard, I choose for that column datatype numeric (DT_NUMERIC - precision 10, scale 2), the Import doesn't start and occurs the error:

- Executing (Error)

Messages

Error 0xc02020a1: Data Flow Task: Data conversion failed. The data conversion for column "PRED_CEL " returned status value 2 and status text "The value could not be converted because of a potential loss of data.".
(SQL Server Import and Export Wizard)

Is it always a precision of 10, and a scale of 2? You may have some inconsistent data. There's two things you could do.

1) Increase the precision and scale.

or

2) Create a custom SSIS package, and redirect the error rows to see where the data inconsistency is. The Import/Export Wizard is great for straight forward tasks, but you'll find that with the smallest blib you'll need to create a custom package.

|||The import is very picky about number formats when importing from flat files. It will NOT import zero padded numbers into a decimal field. Even though it will implicetly convert it internally.

For example:
3.99 - OK
003.99 - FAILS
+003.99 - OK
-003.00 - OK

If you import "003.99" into a varchar(12) and then update a decimal(10,2), with the value of teh varchar, it will work fine.