|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by qz8dsw in MS SQL Server
Hi all,
I have a need to create a 100 gig database in SQL 2000 with 1 table populated with anything really.
The content doesn't really matter.
Given the absence of the amount of data to populate the database to make it that size and the need to make this database quickly is the a SQL way to do this?
I was thinking of inserting the same 1 meg binary file 100,000,000 times as a blob at first thought, but thought An ideal solution would be 1 table in the database, 1 primary key (auto populated) 6 columns (all varchar), populated with random data.
But thats more a dream scenario I think. :)
I'd ask here to see if there is a better way.
Any advice would be appriciated.
Thanks,
Terry
20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625