Default column causing problems!

Hi everybody,

Iam migrating a table called Vendors from sql 2005 to flatfile.

but it end with error message that the default column is causing problem.

the table is as follows,

CREATE TABLE VENDORS

(

RECORDTYPECHAR(5)DEFAULT'VNDRS' NULL,

SETIDCHAR(5)NOT NULL,

VENDORIDCHAR(10)NOT NULL,

VENDORNAMESHORTCHAR(14)NOT NULL,

VENDORNAMESEQNUMINTNULL,

NAME1CHAR(40)NOT NULL,

NAME2CHAR(40)NULL,

REMITVENDORCHAR(10)NULL,

CUSTSETIDCHAR(5)NULL,

CUSTIDCHAR(15)NULL,

ENTEREDBYCHAR(8)NULL,

ARNUMCHAR(15)NULL,

OLDVENDORIDCHAR(15)NULL,

WTHDSWCHAR(1)NOT NULL,

VATSWCHAR(1)NOT NULL,

NAME1ACCHAR(40)NULL,

NAME2ACCHAR(40)NULL,

PRIMARYVENDORCHAR(10)NULL,

LASTACTIVITYDTDATETIMENULL,

HUBZONECHAR(1)NOT NULL,

EEOCERTIFDTDATETIMENULL,

VENDORAFFILIATECHAR(5)NULL

)

any idea as what i need to do?

pls help out.

Thanks and Regards,

sg

You haven't told us anything. What's the error and what are you doing to get that error?|||Why did you create a new thread? This is a duplicate. Please send all responses to the original: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074510&SiteID=1|||

Phil Brammer wrote:

Why did you create a new thread? This is a duplicate. Please send all responses to the original: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074510&SiteID=1

The 2 threads have been merged together

|||

Rafael Salas wrote:

Phil Brammer wrote:

Why did you create a new thread? This is a duplicate. Please send all responses to the original: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074510&SiteID=1

The 2 threads have been merged together

Thanks! You're the man.|||

Hi Phil,

it says the column recordtype which is the default colummn in my case is failing.

so the rows are not getting copied into flat file .

moreover it aslo says that maxerrorcount is 1 and no.of errors exceeded the maxerrorcount,i even tried to change the

maxerrorcount by going to the properties tab.

but still iam getting the error repeatedly.

pls help.

regards,

sg

|||

swan_sg wrote:

Hi Phil,

it says the column recordtype which is the default colummn in my case is failing.

so the rows are not getting copied into flat file .

moreover it aslo says that maxerrorcount is 1 and no.of errors exceeded the maxerrorcount,i even tried to change the

maxerrorcount by going to the properties tab.

but still iam getting the error repeatedly.

pls help.

regards,

sg

Please don't summarize the error in your own words. Please copy and paste the error here. Also, how do you have your data flow setup? Please identify all of the steps and what components you have in your data flow.

Thanks,

Phil

default column causing problem!

Hi everybody,

Iam migrating a table called Vendors from sql 2005 to flatfile.

but it end with error message that the default column is causing problem.

the table is as follows,

CREATE TABLE VENDORS

(

RECORDTYPECHAR(5)DEFAULT'VNDRS' NULL,

SETIDCHAR(5)NOT NULL,

VENDORIDCHAR(10)NOT NULL,

VENDORNAMESHORTCHAR(14)NOT NULL,

VENDORNAMESEQNUMINTNULL,

NAME1CHAR(40)NOT NULL,

NAME2CHAR(40)NULL,

REMITVENDORCHAR(10)NULL,

CUSTSETIDCHAR(5)NULL,

CUSTIDCHAR(15)NULL,

ENTEREDBYCHAR(8)NULL,

ARNUMCHAR(15)NULL,

OLDVENDORIDCHAR(15)NULL,

WTHDSWCHAR(1)NOT NULL,

VATSWCHAR(1)NOT NULL,

NAME1ACCHAR(40)NULL,

NAME2ACCHAR(40)NULL,

PRIMARYVENDORCHAR(10)NULL,

LASTACTIVITYDTDATETIMENULL,

HUBZONECHAR(1)NOT NULL,

EEOCERTIFDTDATETIMENULL,

VENDORAFFILIATECHAR(5)NULL

)

any idea as what i need to do?

pls help out.

Thanks and Regards,

sg

You haven't told us anything. What's the error and what are you doing to get that error?|||Why did you create a new thread? This is a duplicate. Please send all responses to the original: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074510&SiteID=1|||

Phil Brammer wrote:

Why did you create a new thread? This is a duplicate. Please send all responses to the original: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074510&SiteID=1

The 2 threads have been merged together

|||

Rafael Salas wrote:

Phil Brammer wrote:

Why did you create a new thread? This is a duplicate. Please send all responses to the original: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074510&SiteID=1

The 2 threads have been merged together

Thanks! You're the man.|||

Hi Phil,

it says the column recordtype which is the default colummn in my case is failing.

so the rows are not getting copied into flat file .

moreover it aslo says that maxerrorcount is 1 and no.of errors exceeded the maxerrorcount,i even tried to change the

maxerrorcount by going to the properties tab.

but still iam getting the error repeatedly.

pls help.

regards,

sg

|||

swan_sg wrote:

Hi Phil,

it says the column recordtype which is the default colummn in my case is failing.

so the rows are not getting copied into flat file .

moreover it aslo says that maxerrorcount is 1 and no.of errors exceeded the maxerrorcount,i even tried to change the

maxerrorcount by going to the properties tab.

but still iam getting the error repeatedly.

pls help.

regards,

sg

Please don't summarize the error in your own words. Please copy and paste the error here. Also, how do you have your data flow setup? Please identify all of the steps and what components you have in your data flow.

Thanks,

Phil

sql

DecimalPlaces Property

I've got a SQL table that I created through the Access 2K2 interface that is
suddenly giving me a warning message each time I attempt to open the table
in design mode or datasheet mode which says:
"The setting for the DecimalPlaces property must be from 0 through 15, or 25
5 for Auto (default)."
I have checked, rechecked, and checked again the format for every item in my
table, and none of them have a DecimalPlaces property outside of this range
. In fact, only three smallmoney fields have any DecimalPlaces setting at al
l - each is 0. The rest of
the numeric fields are all specified as General Number, and the Decimal Plac
es property is blank (and inaccessible). I have been completely unable to fi
nd any information on this on SQL Server BOL, the KB or these newsgroups. Ha
s anyone else encountered t
his behavior? Any idea why it may be occurring, and what I can do to stop it
? BTW, this is a new table with no data, and the warning message only recent
ly started appearing - it didn't always do so.
TIA,
Terry Roberts>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
--
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||Eric,
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try
a post to the Access newsgroup.
Terry

DecimalPlaces Property

I've got a SQL table that I created through the Access 2K2 interface that is suddenly giving me a warning message each time I attempt to open the table in design mode or datasheet mode which says:
"The setting for the DecimalPlaces property must be from 0 through 15, or 255 for Auto (default)."
I have checked, rechecked, and checked again the format for every item in my table, and none of them have a DecimalPlaces property outside of this range. In fact, only three smallmoney fields have any DecimalPlaces setting at all - each is 0. The rest of
the numeric fields are all specified as General Number, and the Decimal Places property is blank (and inaccessible). I have been completely unable to find any information on this on SQL Server BOL, the KB or these newsgroups. Has anyone else encountered t
his behavior? Any idea why it may be occurring, and what I can do to stop it? BTW, this is a new table with no data, and the warning message only recently started appearing - it didn't always do so.
TIA,
Terry Roberts
>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Eric,
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try a post to the Access newsgroup.
Terry

DecimalPlaces Property

I've got a SQL table that I created through the Access 2K2 interface that is suddenly giving me a warning message each time I attempt to open the table in design mode or datasheet mode which says
"The setting for the DecimalPlaces property must be from 0 through 15, or 255 for Auto (default).
I have checked, rechecked, and checked again the format for every item in my table, and none of them have a DecimalPlaces property outside of this range. In fact, only three smallmoney fields have any DecimalPlaces setting at all - each is 0. The rest of the numeric fields are all specified as General Number, and the Decimal Places property is blank (and inaccessible). I have been completely unable to find any information on this on SQL Server BOL, the KB or these newsgroups. Has anyone else encountered this behavior? Any idea why it may be occurring, and what I can do to stop it? BTW, this is a new table with no data, and the warning message only recently started appearing - it didn't always do so
TIA
Terry Roberts>
> I've got a SQL table that I created through the Access 2K2
> interface that is suddenly giving me a warning message each time
> I attempt to open the table in design mode or datasheet mode
> which says:
> "The setting for the DecimalPlaces property must be from 0
> through 15, or 255 for Auto (default)."
--
Hi Terry,
Try deleting the linked table in Access and relink. See if the problem goes
away.
If the problem persists, post your question in one of the Microsoft Access
forums and someone might be able to help.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||Eric
Thanks for the advice - unfortunately, it didn't solve the problem. I'll try a post to the Access newsgroup
Terry

Debugging stored procedures in SQL2005

I am getting following error message while trying to step into stored procedue:

"Unable to start T-SQL Debugging. Could not connect to computer 'xxx'. The referenced account is currently locked out and may not be logged on to"

I use VS 2005 Professional edition. SQL Server Authentication is used to create data connection in Server Explored. SQL/CLR debugging is enabled for the connection. I followed all steps from this article:

Setting Up SQL Debugging http://msdn2.microsoft.com/en-us/library/s4sszxst(VS.80).aspx

Any help?

Thanks

Slava

It sounds like your password has expired. You can change your password using SQL Server management studio, or you can ask a system administrator to do it for you.

Debugging a stored procedure

When I try to debug stored procedure in SQL Server 2000 Query Analyzer I got error message

SP debugging may not work propertly if you log as 'Local system account' while SQL Server is configured to run as service. You can open Event Viwer to see details ...

After this msgbox I press F5 to start and got error

Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger on COMPAQ-NX6325\PRERADA_MESA (Error = 0x800401f3). Ensure that client-side components, such as SQLLE.DLL, are installed and registered on COMPAQ-NX6325. Debugging disabled for connection 55.

What I have to do to work with debugerWhen I try to debug stored procedure in SQL Server 2000 Query Analyzer I got error message

SP debugging may not work propertly if you log as 'Local system account' while SQL Server is configured to run as service. You can open Event Viwer to see details ...

After this msgbox I press F5 to start and got error

Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger on COMPAQ-NX6325\PRERADA_MESA (Error = 0x800401f3). Ensure that client-side components, such as SQLLE.DLL, are installed and registered on COMPAQ-NX6325. Debugging disabled for connection 55.

What I have to do to work with debuger|||try this code in sql new query editor & execute

sp_Configure 'clr enabled',1
Go
Reconfigure
Go|||This belongs in the SQL Server forum, so this thread will be moved.

moderator|||Please do not double post.


Changed title and merged duplicate threads.

debugger

Hello,
I got the following error message when I was trying to debug a stored
procedure sitting on a remote sql database server. I have no problem
running the debugger on the local server. It just don't work if I try to
debug a stored procedure on a different server. Here is the error message I
got from query analyzer:
Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on QAIMGSQL01 (Error = 0x80070005). Ensure that client-side components, such
as SQLDBREG.EXE, are installed and registered on DVO-D1. Debugging disabled
for connection 74.
Any input is highly appreciated.
Thanks,
LianneLianne Kwock (LianneKwock@.discussions.microsoft.com) writes:
> I got the following error message when I was trying to debug a stored
> procedure sitting on a remote sql database server. I have no problem
> running the debugger on the local server. It just don't work if I try
> to debug a stored procedure on a different server. Here is the error
> message I got from query analyzer: >
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to
> debugger on QAIMGSQL01 (Error = 0x80070005). Ensure that client-side
> components, such as SQLDBREG.EXE, are installed and registered on
> DVO-D1. Debugging disabled for connection 74.
Which version do you have of the client tools? (Visible under Help->About)
Which version is the remote SQL Server? (SELECT @.@.version)
Are you running Windows XP SP2, and have the firewall enabled?
If you XP SP2 with the firewall, both the client tools and the server
needs to be on Service Pack4 for SQL 2000. Futhermore, you need to
configure the firewall, so that SQL Server can access port 135 (RPC) on
your machine. Click the Windows Firewall applet in the Control Panel,
and go the Exceptions tab and select Add Port. In this dialog, be sure
to use Change Scope to open the port only for the SQL Server machine.
And when you've done all this, you may find that it still does not
work. I had i working at the office for a while when we had gotten
hotfix 8.00.944, a pre-SP4 fix. Then our symin changed something;
I think the priveleges of the service account for SQL Server. I have
since then given up on SQL debugging. It is just too much hassle.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I too had similar problems, and essentially, like Erland mentioned, gave up
on remote debugging. Debugging can be handy, so when I really need it, I
actually copy the database locally, so I can debug.
Jef
"Lianne Kwock" <LianneKwock@.discussions.microsoft.com> wrote in message
news:2909E993-E2FA-4F4E-863F-39F95A97F987@.microsoft.com...
> Hello,
> I got the following error message when I was trying to debug a stored
> procedure sitting on a remote sql database server. I have no problem
> running the debugger on the local server. It just don't work if I try to
> debug a stored procedure on a different server. Here is the error message
> I
> got from query analyzer:
>
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to
> debugger
> on QAIMGSQL01 (Error = 0x80070005). Ensure that client-side components,
> such
> as SQLDBREG.EXE, are installed and registered on DVO-D1. Debugging
> disabled
> for connection 74.
>
> Any input is highly appreciated.
>
> Thanks,
> Lianne
>

Debug Stored Procedure - Visual Studio 2003 - Possible?

I can not step into stored procedures that I have created using the VS IDE.
This is the error message that I receive when attempting to debug the stored
procedure:
"Cannot debug stored procedures because the SQL Sserver database is not
setup correctly or user does not have permission to execute
master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
I am the database administrator! I have sp_sdidebug set to legacy_on. Not
sure what else to try. My boss does not want to pay for SQL Server Dev
edition, so I would really like to get this working.
Any suggestions will be greatly appreciated.
Thank you,
Michael Garcia
If your boss doesn't want to shell out $49 for the Developer Edition,
perhaps you could helpfully point out that many experienced people
have spent countless hours attempting to get debugging working from
the VS IDE, and have failed to do so. To obtain actual evidence, do a
google groups search on the topic and read threads from other
frustrated users. Ask him to consider how much he is paying you by the
hour, counting benefits, and then ask him to do the math. Caveat --
you can't use the Developer edition as a production server, but it's
indispensable if you care anything about creating a secure and robust
database app.
--Mary
On Tue, 19 Oct 2004 09:19:03 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:

>I can not step into stored procedures that I have created using the VS IDE.
>This is the error message that I receive when attempting to debug the stored
>procedure:
>"Cannot debug stored procedures because the SQL Sserver database is not
>setup correctly or user does not have permission to execute
>master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
>I am the database administrator! I have sp_sdidebug set to legacy_on. Not
>sure what else to try. My boss does not want to pay for SQL Server Dev
>edition, so I would really like to get this working.
>Any suggestions will be greatly appreciated.
>Thank you,
>Michael Garcia
|||Your point is noted; however, I got it working yesterday.
For all those that are having problems getting debugging working in VS for
MSDE try this!
First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
..NET 2003\sqlserver
Copy it to the binn directory of your MSDE instance.
Second run dcomcnfg.
Component Services -> Computers -> My Computer
Select properties for My Computer. Go to the Default COM Security tab.
Edit the default settings for access permissions. Add yourself and system
if it is not there and make sure allow is checked.
This got it working on both my systems.
Good luck!
Michael Garcia
"Mary Chipman" wrote:

> If your boss doesn't want to shell out $49 for the Developer Edition,
> perhaps you could helpfully point out that many experienced people
> have spent countless hours attempting to get debugging working from
> the VS IDE, and have failed to do so. To obtain actual evidence, do a
> google groups search on the topic and read threads from other
> frustrated users. Ask him to consider how much he is paying you by the
> hour, counting benefits, and then ask him to do the math. Caveat --
> you can't use the Developer edition as a production server, but it's
> indispensable if you care anything about creating a secure and robust
> database app.
> --Mary
|||You're lucky -- others have hit the wall configuring DCOM and dealing
with SP2 issues. Please have your boss get you the Dev edition anyway
-- there are many things you simply cannot do from the VS IDE unless
you want to write a lot of script.
--Mary
On Wed, 20 Oct 2004 09:39:02 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Your point is noted; however, I got it working yesterday.
>For all those that are having problems getting debugging working in VS for
>MSDE try this!
>First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
>.NET 2003\sqlserver
>Copy it to the binn directory of your MSDE instance.
>Second run dcomcnfg.
>Component Services -> Computers -> My Computer
>Select properties for My Computer. Go to the Default COM Security tab.
>Edit the default settings for access permissions. Add yourself and system
>if it is not there and make sure allow is checked.
>This got it working on both my systems.
>Good luck!
>Michael Garcia
>"Mary Chipman" wrote: