Viewing 15 posts - 151 through 165 (of 813 total)
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...
January 21, 2014 at 10:13 am
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...
January 21, 2014 at 9:10 am
Are you using dynamic ports, or a fixed port?
Firewall?
January 21, 2014 at 8:55 am
Jeff Moden (1/20/2014)
devu (1/20/2014)
Hi all,I want to know which is the faster group of select statement or stored procedure with same select statements ?
Thanks.
My question would be, why don't you...
January 21, 2014 at 8:53 am
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...
January 21, 2014 at 8:51 am
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 -...
January 21, 2014 at 8:39 am
GilaMonster (1/20/2014)
exec sp_recompile 'procedure name' removes that plan from cache completely. I have...
January 20, 2014 at 8:48 am
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...
January 17, 2014 at 1:14 pm
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",...
January 17, 2014 at 1:09 pm
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...
January 17, 2014 at 11:41 am
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...
January 14, 2014 at 1:01 pm
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...
January 14, 2014 at 12:54 pm
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...
January 14, 2014 at 9:11 am
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...
January 14, 2014 at 8:56 am
hisakimatama (1/13/2014)
It seems that this problem was fixed in a...
January 14, 2014 at 8:42 am
Viewing 15 posts - 151 through 165 (of 813 total)