Use Wireshark or whatever other packet sniffer simultaneously on both the client machine and the SQL Server machine; keep them running from the time it's working until it's not, then...

I doubt it - check your SQL Server logs at those times. Also, perhaps turn on logging of both successful and failed logins - look for patterns at the...

Are you using dynamic ports, or a fixed port?

Firewall?

Jeff Moden (1/20/2014)

---

My question would be, why don't you...

Personally, whenever I have enough time in my maintenance windows, I either don't touch an index, or I rebuild it - I almost never reorganize, as rebuild gives you better...

I'll join in - nice script, Perry! It's got more of the options than the one I use.

SQL 2005, 2008, and 2008R2 all use 2005-vintage "0x0100" prefix passwords -...

GilaMonster (1/20/2014)

---

You'd need to explain more what you did for me to be able to say what happened there.

exec sp_recompile 'procedure name' removes that plan from cache completely. I have...

Try something more like the SQL2008 one of these - use the source database's version of native client as your @provider, essentially.

-- FROM 2012

EXEC master.dbo.sp_addlinkedserver @server...

Good discussion - I apparently missed it.

I would note that with TDE or other encryption technologies, if you're trying to accomplish a goal beyond circling yes on "Encryption: Yes/No",...

Ok, a slightly improved version of the script above, with a CASE statement that can validate password guesses, and which that should make things much more clear.

--If you need a...

Did you try the script I just posted? The original had an error; I'll update that post.

No, there's just the one salt, 4 bytes long.

SQL2012:

0x0200

ABCDEF12 - salt

xxxxx - SHA-512...

It's SHA-512; however, SHA-512 is longer than SHA1!

EDIT: Use the version from my post later on in this thread

-- 2005 through 2012+ variants

SELECT sl.name

, sp.type

, sl.sysadmin

, CAST(sl.password AS VARBINARY(384)) AS...

Try looking at the password, then.

You can start with something like this:

See my later post - remember, SHA1 is 160 bits, SHA-256 is 256 bits, and SHA-512 is 512 bits.

If...

Also see sites like http://sqlserverbuilds.blogspot.com/[/url].

Note that opinions vary. My general go-to methodology is:

Apply all SP's a couple weeks after they come out (every once in awhile, they cause major...

hisakimatama (1/13/2014)

---

Aha! With what Jeff mentioned, it seems that you may indeed be a victim of the aforementioned bug:

Microsoft Fix Notes

It seems that this problem was fixed in a...