Forum Replies Created

Viewing 15 posts - 46 through 60 (of 92 total)

  • RE: Wide table performance issue

    I know these kind of questions are going to pop up. But thats for future.

    Right now, the immediate concern is redesign of tables to at least showcase the capability...

  • RE: Wide table performance issue

    The reason for 7 years of data archival is because sometimes the executives query for a particular customer. For example what was the purchase amount for customer X between a...

  • RE: Wide table performance issue

    You are the guru Ninja. I am going to stick by your wisdom 🙂

  • RE: Wide table performance issue

    Another question for you guys. Will it really matter if I choose NVARCHAR or VARCHAR for the data type? If I keep it as unicode data type, I dont have...

  • RE: Wide table performance issue

    @steve-2 Cullen

    You are right. The ODBC Connection (read query) to pull data from the table was originally based in an excel. Now since I am the only...

  • RE: Wide table performance issue

    Thats a design issue that I need to take up with my boss. He wants all the data (Yes, the entire 7 years) ready to be reported. No archival. Now...

  • RE: Wide table performance issue

    Oops..Bad math hits me again :D. You are right Ninja. Your count seems to be right.

  • RE: Wide table performance issue

    Thanks for all your suggestions people. I am really glad to learn a lot of new things from you guys. 🙂

  • RE: Wide table performance issue

    Yes. The SQL_POST_DATE is indeed a string. But the AW_POST_DATE is a datetime format column and using that too did not offer any performance improvement. As of now, I have...

  • RE: Wide table performance issue

    Sorry for the late reply folks. Took a long nap to overcome my stupidity while designing this table.

    Here's the deal that I deduced from much of the discussion going...

  • RE: Wide table performance issue

    SQL_POST_DATE and AW_POST_DATE are one and the same. I realized that and change my query to use AW_POST_DATE which is indeed a datetime field. But still, there's no change to...

  • RE: Wide table performance issue

    LOL...My bad. Here's the DDL. The data types have been verified by my boss and unfortunately enough, he doesnt have any knowledge about SQL Server.

    CREATE TABLE [Sales].[HOWLI_LOAD](

    [ID] [int] IDENTITY(1,1)...

  • RE: Wide table performance issue

    Here's my table definition. I dont have a clustered index in there and the only index that I got is on SQL_POST_DATE. Now as far as I know, this table...

  • RE: Wide table performance issue

    I added a non clustered index on the SQL_POST_DATE, but that didnt make any difference. In fact the numbers went up on my new execution plan. Dont know what's going...

  • RE: Wide table performance issue

    Agreed that a non clustered index would improve performance. I already have something of that sort on a table which is very similar to this one. But I could not...

Viewing 15 posts - 46 through 60 (of 92 total)