SQL Server 2005 Error: 701, Severity: 17, State: 193

anith
2nd June 2009
2008, 2009, 3.0, 4g, action, Administrator, ads, air, analytics, anonymous, app, application, archive, art, atom, att, Blog, build, case, cd, change, cli, client, cloud, code, color, community, connect, Cookie, corrupt, Corruption, course, cpu, css, customer, data, developer, display, drive, ea, EFI, ego, elements, email, engineers, event, events, experience, fix, free, fun, gdc, General, goo, Google, Graham, hack, hd, host, HP, ical, icon, im, increase, Interesting, ion, IT, java, javascript, King, language, languages, lg, library, life, lines, location, lock, long, love, ls, mac, mail, maintenance, march, media, memo, Meta, microsoft, Microsoft Rules, Mini, monitor, nand, new, news, NIN, office, oled, open, order, OS, pc, perform, performance, php, plan, play, port, post, pre, pro, problem, Q1, rant, resources, retro, retrospect, rights, rip, rss, screen, script, search, server, shoot, shooting, source, ssd, store, support, syndication, tag, tags, tasks, tech, techno, theme, themes, time, tip, tips, tool, toolbox, top, tor, track, trends, troubleshooting, TV, twitter, ui, uk, unity, update, value, wind, word, worker
2008, action, anonymous, app, application, archive, atom, att, build, case, cli, client, code, Cookie, cpu

Here’s another interesting example which we worked recently in the Stockholm office, which relates also back to one of my previous entries. We had a customer whose error log was filled with a variety of critical errors such as these: Error: 701, Severity: 17, State: 193.

Read more from the original source:
SQL Server 2005 Error: 701, Severity: 17, State: 193

SQL Server 2005 Error: 701, Severity: 17, State: 193

Leave a comment