Why are the table name different from 2000 v 2005 for ASPState DB

  • I created both aspsate databases by running installsqlstate.sql, then aspnet_regsql. Why are the

    2000 ASPState tables different then 2005. The 2000 Tables all start with all start with sys... and 2005 are all aspnet_.... Why is that?

    all little back ground information about how I created the databases.

    When I ran InstallSQLState.sql in 2000 I got this error, but it created the database anyway. I then could use aspnet_regsql.exe and point to that databse to create the system tables.

    If the category already exists, an error from msdb.dbo.sp_add_category is expected.

    Server: Msg 14261, Level 16, State 1, Procedure sp_add_category, Line 32

    The specified @name ('[Uncategorized (Local)]') already exists.

    When I ran InstallSQLState.sql in 2005 I got this error, but it created the database anyway. I then could use aspnet_regsql.exe and point to that databse to create the system tables.

    If the job does not exist, an error from msdb.dbo.sp_delete_job is expected.

    If the category already exists, an error from msdb.dbo.sp_add_category is expected.

    Msg 14261, Level 16, State 1, Procedure sp_add_category, Line 32

    The specified @name ('[Uncategorized (Local)]') already exists.

  • your post is rather confusing.

    Perhaps you can step back and explain what you were trying to do. The .sql files you specified must be from some application or framework. Please note that.

    Also, please italicize or otherwise show the error off. It's hard to tell where your text stops and the error starts.

    From the error, it appears you're trying to add a job category that already exists.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply